Jump to content

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


Kobymaru

Recommended Posts

  • 1 month later...
  • 4 weeks later...
  • 3 weeks later...

I'm not getting an accurate trajectory in 1.11.2, it doesn't seem to be accounting for atmospheric drag. Was FAR compatibility broken at some point?

EDIT: NVM, reinstalled FAR, problem solved

Edited by dlrk
Link to comment
Share on other sites

Does anyone know why when I plan an Aerocapture maneuver on Laythe with my SSTO and I get the X to be directly on a spot I want on my manuever, it moves later? While set to Prograde in the descent profile at 0 Degrees it changes to be completely off mark when I'm just about to enter the atmosphere. I'm still facing prograde; I don't know what's going on.

Am I missing something?

X marks the spot here:

voxUarA.png

 

X doesn't mark the spot here: veers off way before my target despite nothing changing and me facing the correct direction I had plotted for reentry (0 degrees from prograde)

IE3W4eQ.png

Edited by rudemario
Grammar
Link to comment
Share on other sites

14 minutes ago, dlrk said:

Do you have body fixed mode selected?

As far as I'm aware it doesn't make much of a difference when you're measuring specifically body-centric calculations like what happens when you're near the surface of the planet, and it removes the disconnect from the cross and the trajectory line, but no, I don't have it on.

For example, here is the screenshot with it disabled:

HYmJS0W.png

And after I enabled it to show:

Nk5DZAK.png

 

Any other ideas why? I appreciate the help.

Link to comment
Share on other sites

 

On 5/8/2021 at 8:08 PM, rudemario said:

Does anyone know why when I plan an Aerocapture maneuver on Laythe with my SSTO and I get the X to be directly on a spot I want on my manuever, it moves later? While set to Prograde in the descent profile at 0 Degrees it changes to be completely off mark when I'm just about to enter the atmosphere. I'm still facing prograde; I don't know what's going on.

Something I've done to fix that is go through all the zeroes in the descent profile and just click each one and hit enter. Maybe it's showing zero when it's not actually set to zero?

Link to comment
Share on other sites

On 5/9/2021 at 5:08 AM, rudemario said:

Does anyone know why when I plan an Aerocapture maneuver on Laythe with my SSTO and I get the X to be directly on a spot I want on my manuever, it moves later? While set to Prograde in the descent profile at 0 Degrees it changes to be completely off mark when I'm just about to enter the atmosphere. I'm still facing prograde; I don't know what's going on.

This means that the prediction is wrong. There could be a few reasons for this:

  • Predictions in the upper atmosphere are difficult, so if you spend a lot of time there, deceleration will be underestimated.
  • Physics time warp actually changes your trajectory! The higher the time warp, the less drag you experience.
  • Is "Use Cache" enabled in the settings? That increases performance but decreases accuracy.
Link to comment
Share on other sites

  • 2 weeks later...
On 9/2/2020 at 4:54 AM, Nori said:

So I've tried using trajectories to land close to KSC but currently I am always coming up very short with the standard settings. I've tried prograde and retrograde. If I put the red X over KSC I undershoot by a lot. This last time I put it about 170km past and I ended up landing about 80km short. I am using a 2.7x system and the atmo is at 85k. Is there something I should be doing differently?

I have the same problem with the original-scale system on Kerbin. Trajectories 2.4.0, KSP 1.11.2, stock aerodynamic model. Sometimes when I adjust impact position with RCS above or in the upper layers of the atmosphere I can land within 500 meters of the predicted point, but more often I end up undershooting a few dozens km, the shallower the descent, the bigger the error.  At about 45000-50000 m the impact position indicator starts crawling backwards. Sometimes I'm able to check it by adjusting attitude, sometimes not.

I've noticed that when I press "Update" button in the settings during the descend the impact position changes and appears to be closer to where I really land (in fact, it just immediately jumps short of the previous position instead of gradually crawling from it). Can I adjust settings somehow to fix this?

Also,  can I rely on the updates of the impact position indicator when I perform active maneuvering in the upper atmosphere?

Link to comment
Share on other sites

On 5/18/2021 at 12:11 PM, Kobymaru said:

This means that the prediction is wrong. There could be a few reasons for this:

  • Predictions in the upper atmosphere are difficult, so if you spend a lot of time there, deceleration will be underestimated.
  • Physics time warp actually changes your trajectory! The higher the time warp, the less drag you experience.
  • Is "Use Cache" enabled in the settings? That increases performance but decreases accuracy.

Tried without warp whatsoever,  steep descent from 100km Kerbin circular orbit, dv -400m/s, sas on retrograde(just as plugin settings), landed 82km short of the predicted spot.

Edited by olegst90
Link to comment
Share on other sites

44 minutes ago, olegst90 said:

I have the same problem with the original-scale system on Kerbin. Trajectories 2.4.0, KSP 1.11.2, stock aerodynamic model. Sometimes when I adjust impact position with RCS above or in the upper layers of the atmosphere I can land within 500 meters of the predicted point, but more often I end up undershooting a few dozens km, the shallower the descent, the bigger the error.  At about 45000-50000 m the impact position indicator starts crawling backwards. Sometimes I'm able to check it by adjusting attitude, sometimes not.

I've noticed that when I press "Update" button in the settings during the descend the impact position changes and appears to be closer to where I really land (in fact, it just immediately jumps short of the previous position instead of gradually crawling from it). Can I adjust settings somehow to fix this?

Also,  can I rely on the updates of the impact position indicator when I perform active maneuvering in the upper atmosphere?

 

36 minutes ago, olegst90 said:

Tried without warp whatsoever,  steep descent from 100km Kerbin circular orbit, dv -400m/s, sas on retrograde(just as plugin settings), landed 82km short of the predicted spot.

Turned out Cache option was the culprit. With the cache off and max frames and integration step sliders to the rightmost position I managed to obtain very good precision without too much of performance penalty (around 20% of the calculation time on average). Sorry for flooding.

Link to comment
Share on other sites

Heya,

Running KSP 1.11.2.3077 and Trajectories 2.4.0 (& KAC and no other mods), I superficially get what I'd expect to see on the map screen (a red line and a cross), but I don't get any options in the stock toolbar.

I have the following in my log which seems relevant:

[LOG 10:09:07.591] [Trajectories] v2.4.0 Starting
[LOG 10:09:07.595] [Trajectories] Loading settings
[ERR 10:09:07.627] Exception loading ScenarioModule Trajectories: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
  at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 
  at AssemblyLoader+LoadedAssembly.TypeOperation (System.Action`1[T] action) [0x00006] in <06f13185617646e5bc801baeab53ab75>:0 
  at AssemblyLoader+LoadedAssembyList.TypeOperation (System.Action`1[T] action) [0x0001c] in <06f13185617646e5bc801baeab53ab75>:0 
  at Trajectories.ToolbarTypes.getType (System.String name) [0x00014] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.ToolbarManager.get_Instance () [0x00023] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.ToolbarManager.get_ToolbarAvailable () [0x0000c] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.MainGUI+<>c.<Allocate>b__88_38 () [0x00000] in <1599f0119b6e426290c88a610947d26e>:0 
  at DialogGUIToggle..ctor (System.Func`1[TResult] set, System.String lbel, Callback`1[T] selected, System.Single w, System.Single h) [0x00045] in <06f13185617646e5bc801baeab53ab75>:0 
  at Trajectories.MainGUI.Allocate () [0x00f96] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.MainGUI.Start () [0x00007] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.Trajectories.OnLoad (ConfigNode node) [0x0003c] in <1599f0119b6e426290c88a610947d26e>:0 
  at ScenarioModule.Load (ConfigNode node) [0x0000e] in <06f13185617646e5bc801baeab53ab75>:0 
  at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <06f13185617646e5bc801baeab53ab75>:0 

The solution for me here is probably "install Blizzy's toolbar" but in case it's any use to you...

Link to comment
Share on other sites

On 6/6/2021 at 1:56 PM, Rawling said:

Heya,

Running KSP 1.11.2.3077 and Trajectories 2.4.0 (& KAC and no other mods), I superficially get what I'd expect to see on the map screen (a red line and a cross), but I don't get any options in the stock toolbar.

I have the following in my log which seems relevant:

The solution for me here is probably "install Blizzy's toolbar" but in case it's any use to you...

Hi! I can not reproduce this, I installed Trajectories and nothing else, but I did not get those errors in my Log file. Trajectory was displayed correctly.

Is it possible that some settings file was left over from when you had the toolbar installed and enabled?

Link to comment
Share on other sites

On 6/6/2021 at 7:56 AM, Rawling said:

Heya,

Running KSP 1.11.2.3077 and Trajectories 2.4.0 (& KAC and no other mods), I superficially get what I'd expect to see on the map screen (a red line and a cross), but I don't get any options in the stock toolbar.

I have the following in my log which seems relevant:



[LOG 10:09:07.591] [Trajectories] v2.4.0 Starting
[LOG 10:09:07.595] [Trajectories] Loading settings
[ERR 10:09:07.627] Exception loading ScenarioModule Trajectories: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
  at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 
  at AssemblyLoader+LoadedAssembly.TypeOperation (System.Action`1[T] action) [0x00006] in <06f13185617646e5bc801baeab53ab75>:0 
  at AssemblyLoader+LoadedAssembyList.TypeOperation (System.Action`1[T] action) [0x0001c] in <06f13185617646e5bc801baeab53ab75>:0 
  at Trajectories.ToolbarTypes.getType (System.String name) [0x00014] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.ToolbarManager.get_Instance () [0x00023] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.ToolbarManager.get_ToolbarAvailable () [0x0000c] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.MainGUI+<>c.<Allocate>b__88_38 () [0x00000] in <1599f0119b6e426290c88a610947d26e>:0 
  at DialogGUIToggle..ctor (System.Func`1[TResult] set, System.String lbel, Callback`1[T] selected, System.Single w, System.Single h) [0x00045] in <06f13185617646e5bc801baeab53ab75>:0 
  at Trajectories.MainGUI.Allocate () [0x00f96] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.MainGUI.Start () [0x00007] in <1599f0119b6e426290c88a610947d26e>:0 
  at Trajectories.Trajectories.OnLoad (ConfigNode node) [0x0003c] in <1599f0119b6e426290c88a610947d26e>:0 
  at ScenarioModule.Load (ConfigNode node) [0x0000e] in <06f13185617646e5bc801baeab53ab75>:0 
  at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <06f13185617646e5bc801baeab53ab75>:0 

The solution for me here is probably "install Blizzy's toolbar" but in case it's any use to you...

You really need to provide a complete log file.  Snippets are mostly useless without knowing what else and what other errors might be going on.

For example, the log file can provide information as to what mods (and the version of each mod) are installed.  Also, what version of the game is being played. Etc.

Edited by linuxgurugamer
Link to comment
Share on other sites

On 5/7/2021 at 4:44 AM, dlrk said:

I'm not getting an accurate trajectory in 1.11.2, it doesn't seem to be accounting for atmospheric drag. Was FAR compatibility broken at some point?

EDIT: NVM, reinstalled FAR, problem solved

SAME! Sometimes it won't show the landing spot you will get with drag, nor indicate the decrease of your orbit after reentry whatsoever.

Link to comment
Share on other sites

15 hours ago, adriangm44 said:

SAME! Sometimes it won't show the landing spot you will get with drag, nor indicate the decrease of your orbit after reentry whatsoever.

It's FAR v0.16.0.2, it always returns 0 Force. Fortunately, this has been fixed already.

So either revert to v0.16.0.1, build the current master or wait for the next FAR release.

Edited by Kobymaru
Link to comment
Share on other sites

4 hours ago, Kobymaru said:

It's FAR v0.16.0.2, it always returns 0 Force. Fortunately, this has been fixed already.

So either revert to v0.16.0.1, build the current master or wait for the next FAR release.

Thank you mate. Do you know where is v0.16.0.1 posted for download?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...