davidweb
New member
Hello!
I'm trying to understand the GS2 / BaseSync relationship. I'm on Orbiter 2016 and I've tried this first with DGIV then switched to XR2 because I thought maybe the reason for the below issue was that DGIV wasn't technically compatible with 2016... but same issue.
If I undock from ISS, target Cape Canaveral using base sync I get to the right orbit # for reentry etc. When I slave BS to GS with Cape Canaveral RW 15 selected, for example... the "DeltaAZ", Range, info say "-nan(ind)"
Questions:
1) Is this because I am not at the 200km orbit that the default GS parameters of 0.73 degree angle and anticipation refer to? IE: Do those angles vary based on the orbit from which I am doing my de-orbit burn?
2) If so, is there a way without simple guess or trial/error to correct for different orbits? If I'm at a 380km orbit, how would I know or figure out what a better angle / anticipation angle would be?
Hope this makes sense. And thanks in advance for any help you might have!
-David
I'm trying to understand the GS2 / BaseSync relationship. I'm on Orbiter 2016 and I've tried this first with DGIV then switched to XR2 because I thought maybe the reason for the below issue was that DGIV wasn't technically compatible with 2016... but same issue.
If I undock from ISS, target Cape Canaveral using base sync I get to the right orbit # for reentry etc. When I slave BS to GS with Cape Canaveral RW 15 selected, for example... the "DeltaAZ", Range, info say "-nan(ind)"
Questions:
1) Is this because I am not at the 200km orbit that the default GS parameters of 0.73 degree angle and anticipation refer to? IE: Do those angles vary based on the orbit from which I am doing my de-orbit burn?
2) If so, is there a way without simple guess or trial/error to correct for different orbits? If I'm at a 380km orbit, how would I know or figure out what a better angle / anticipation angle would be?
Hope this makes sense. And thanks in advance for any help you might have!
-David