[1.12.x] Trajectories v2.4.5 (2023-08-22) : atmospheric predictions

[dlrk]

8 hours ago, kurgut said:

Hi @Kobymaru , Is there a way so I can see the predicted trajectory after staging, since most of the time, i've got something like reentry pod+service module/engine I decouple before reentry, then the predictions change slightly.

Is that possible, or do I need to eyeball it?

Thanks

The best, and not entirely unrealistic, workaround is to leave little bit of a maneuvering dV on your final stage to clean up the trajectory after staging. Aim for an initial periapsis that has some room to lower and/or raise

[kurgut]

52 minutes ago, dlrk said:

The best, and not entirely unrealistic, workaround is to leave little bit of a maneuvering dV on your final stage to clean up the trajectory after staging. Aim for an initial periapsis that has some room to lower and/or raise

Ye, that's what I went for, and with RCS, it's all right (also set 0 force to the decoupler).

[PiezPiedPy]

19 hours ago, woodbyte said:

Kerbalism works fine with AMP, and the previous version of this mod (2.2.1, no bootloader) exhibits the exact same issue.

hmmm, that's me stumped 

[infinite_monkey]

Is it possible to change the color of the crosshair indicator somewhere? I recently installed SciFi Visual Enhancements, and on Duna it's REALLY hard to see the indicator in full daylight.

[PiezPiedPy]

2 hours ago, infinite_monkey said:

Is it possible to change the color of the crosshair indicator somewhere? I recently installed SciFi Visual Enhancements, and on Duna it's REALLY hard to see the indicator in full daylight.

Currently the colour is set in the code, so no unless you make a private build.

[Devoblue]

On a fresh install of 1.7.0 this mod (v2.2.2) doesn't work, but after copying the file \GameData\Trajectories\Plugin\Trajectories16.bin to Trajectories17.bin, limited testing indicates it still works fine.

[OrbitsR4Sissies]

I just noticed this, too.

When in the VAB, there's a strange error to most of my spacecraft. Something like "Unknown Trajectories Module."

The mod's toolbar button doesn't appear after loading a fresh copy.

I'll consider that workaround until things are updated.

[OrbitsR4Sissies]

On 4/11/2019 at 7:26 AM, Devoblue said:

On a fresh install of 1.7.0 this mod (v2.2.2) doesn't work, but after copying the file \GameData\Trajectories\Plugin\Trajectories16.bin to Trajectories17.bin, limited testing indicates it still works fine.

Looking at the 2.2.2 folder, I found Trajectories13.bin, 14, 15, and 16.bin. Didn't find a 17.bin in that or the 2.2.1 folder. Can you point us to where that 17.bin file was and where to place it again?

[dok_377]

15 hours ago, OrbitsR4Sissies said:

Looking at the 2.2.2 folder, I found Trajectories13.bin, 14, 15, and 16.bin. Didn't find a 17.bin in that or the 2.2.1 folder. Can you point us to where that 17.bin file was and where to place it again?

You just need to make a copy of Trajectories16 and rename it to Trajectories17. That's it. 

Edited April 13, 2019 by dok_377

[MechBFP]

Can confirm this appears to be working fine in 1.7 for me as well once making that new bin file. 

Its terribly inaccurate on Eve still though.

[Tuupertunut]

Yeah, the downside of having version specific binaries is that it's no longer compatible with future versions.

Fix suggestion: If a newer version is detected, make it load the latest binary.

[Kilo60]

Is there any way to get this to work with 1.7?

[3PoundsOfFlax]

5 hours ago, Kilo60 said:

Is there any way to get this to work with 1.7?

Yes, go to \GameData\Trajectories\Plugin and rename Trajectories16.bin to Trajectories17.bin

[Brigadier]

15 hours ago, Kilo60 said:

Is there any way to get this to work with 1.7?

The answer was three posts above yours.  It is generally accepted practice that one reads the last couple of pages of a thread to which one is a new visitor before posting problems just to see if the issue has been addressed already.  It saves on people repeating themselves.

[dlrk]

This still being worked on?

[Kobymaru]

On 5/13/2019 at 8:45 PM, dlrk said:

This still being worked on?

I'm busy with real life, and looks like PiezPiedPy is too. We could probably push out a point release for 1.7 compatibility, but it would basically be a recompile and wouldn't have new stuff in it.

[Elon Kerman Jr]

I think I installed the mod maybe wrong as its in my gamedata but I cant see or use it ingame

[Blothorn]

Did you rename /GameDataTrajectories/Plugin/Trajectories16.bin to Trajectories17.bin? (If not, this is the third time it's been mentioned on this page alone; *please* read the last few pages of a mod's thread before asking support questions.)

Edited May 16, 2019 by Blothorn
typo

[Peter Ferreira]

On 4/19/2019 at 1:52 AM, 3PoundsOfFlax said:

Yes, go to \GameData\Trajectories\Plugin and rename Trajectories16.bin to Trajectories17.bin

I had copied Trajectories16.bin to Trajectories17.bin and replaced the 8 line from \GameData\Trajectories\Trajectories.version.

This specific line is now "KSP_VERSION_MAX":{"MAJOR":1,"MINOR":7,"PATCH":1}

Is working now.

[N70]

Hey, I suggest ya'll change the .bin to .kbin, for Kopernicus 1.7.1 compat, like I had to do for Kerbalism.

[dlrk]

A recompile for 1.7.1 compatibility would definitely be good for now

[dlrk]

On 6/7/2019 at 8:03 PM, N70 said:

Hey, I suggest ya'll change the .bin to .kbin, for Kopernicus 1.7.1 compat, like I had to do for Kerbalism.

Does it work OK once that's been changed?

[N70]

41 minutes ago, dlrk said:

Does it work OK once that's been changed?

Yes, but you can't just rename them to .kbin, it won't work.

It has to be changed code-side on the mod.

[dlrk]

Anyone got a compiled one to share?

[N70]

8 hours ago, dlrk said:

Anyone got a compiled one to share?

Just rename Trajectories16.bin to Trajectories.dll, delete the other .bins and the bootstrap.