Share this post

Link to post

Share on other sites

I loaded up Trajectories 1.1.1.0-pre1 and FAR 0.14.6 in which ferram fixed the bug causing trajectories to lock up the game and now I get a repeating error from Trajectories whenever it tries to run in atmosphere. It also doesn't seem to know what aero model is being used.

Here's my output.log for this error. Errors start at line 40365 and stop at line 311580 with 12,364 of the same error. Anyone else getting this, or have they managed to get Trajectories and FAR to work together? I have a lot of other mods, so there may be some other conflict.

No crash, game keeps running, but the errors just start racking up quickly and trajectories fails to show anything on the map.

Share this post

Link to post

Share on other sites

Thanks, I will look into that. Stock revamp has nothing to do with it; apparently there's an incompatibility between NEAR and trajectories that needs to be fixed. Stay tuned for updates.

In the meanwhile I'll check if revamp has anything to do with this anyway, it modified some stuff related to stock cockpits that, as I recall, causes invalid drag calculation by FAR/NEAR for them (I guess because of added intakes), though my test ship used only stock landing pod+tank+engine, so it had no aerodynamics/SPH related parts.

Update: seems like revamp had nothing to do with this, same error spam happens after it has been removed.

Share this post

Link to post

Share on other sites

Suggestion (no idea if thats possible): When i do a retroburn for reentry i use my service module for it, which is jettisoned before i hit the atmosphere. This means that while im burning for an accurate reentry it calculates for a reentry with the service module still attached, this trajetory is changed when i decouple the service module from my capsule. I would love an option that calculates the landing spot after the next staging event (for the then smaller craft), this would increase the accuracy of my reentrys very much...