- Joined
- Jan 7, 2008
- Messages
- 5,790
- Reaction score
- 780
- Points
- 203
- Location
- Earth
- Website
- orbides.org
- Preferred Pronouns
- she/her
Alpha 100319 below.
There should be no way to access scram engines without vessel support, so if you sure you found a repeatable bug that does just that, please tell the way to repeat it.
It does not have any completion conditions, like final altitude, only holds state for eternity.
You can specify altitude it will hold, and you can specify the climb rate - rate of change of that altitude value. Same for other two.
---------- Post added at 19:16 ---------- Previous post was at 15:15 ----------
Alpha 100319:
orbides.1gb.ru/orbf/uap-alpha-100319.zip
Changes:
-Grand optimization of Sync Orbits AP
-More careful plane aligning, should use one node most of the times
-Added wait for other vessel's sequence completion in vessel tool
-Added heading to trans-orbital
-Added undocking tool
-Added status string
-Fixed state of sequence running save
Bugfixes and optimizations.
The Sync orbits should now be much more consistent and precise, selecting the manoeuvres better.
Align planes should take one node most of the time on small changes, so Martian chase now completes within one orbit, Sync+Align.
These two are the targets of this alpha, as well as any bugs.
What next?
-Moon to Earth?
-Into the big interplanetary void?
-Landings and re-entries?
-OrbitHanger?
One potential difficulty with the Hohmann AP was that it began the Moon insertion burn much earlier than I'd expected. As a result, the final PeA was 150 km lower than had been programmed (600 km), for a 25% error from the programmed altitude.
Strange, it always work quite accurate for me, with various moons. Can either of you post a full scenario with near-encounter position that would fail like that?Hohmann transfer worked well, but like mjanicki, it put me in a far lower orbit than I had set.
I don't think so, scram engines are not default, and thus cannot be accessed without vessel-side support.This was the first time I've used a DG with UAP, and it got me thinking. Is it possible to add Scram jet settings into lift off and runway off?
It was supposed to mean - set the mode before running.And why does tools have -1 set as the mode default? That's not a valid input. (But "mode_is: WTF?" is very amusing nonetheless. :lol
Not as easy as it sounds, i'll keep it in mind.Small request. Any way for "Heading = X " to carry over into next step? Just so I don't have to worry about whether I kept it consistent through the various steps.
Huh? Engine=15 will make it use all engines - hover, retro, main and main upside-down, causing a big confused tumbling ball of exhausts. For DG at least.Also, is "Engine = 15 " the only way to get a SCRAM engine going through Aerial Hold? It works well enough if that's the case, just curious.
There should be no way to access scram engines without vessel support, so if you sure you found a repeatable bug that does just that, please tell the way to repeat it.
You're understanding it wrong.Another thing: When in Aerial Hold AP, how can I change "alt_rate" without raising "altitude"? I'm trying to get a good Aerial Hold AP sequence for the XR2 Ravenstar's SCRAM cruise phase. For example; have a final "altitude" of 70000 with an "alt_rate" of 100 m/s, with an "engine" of 15(see above), and "velocity" of 6300 in an Aerial Hold sequence. Am I just doing it wrong because I don't completely understand the "onoff"?
It does not have any completion conditions, like final altitude, only holds state for eternity.
You can specify altitude it will hold, and you can specify the climb rate - rate of change of that altitude value. Same for other two.
Fixed.I'm pretty sure every time I open a saved scenario with a UAP sequence, it automatically runs the AP when the scenario starts.
Ok, i've added a heading variable to it, if it's targeted (heading read from target), or heading is set to 0..360 it will follow the heading, if heading is set to -1, it will follow prograde.At the moment it is not possible to launch into a specific orbital plane unless there is already a vessel orbiting in that plane for the autopilot to use as a target.
---------- Post added at 19:16 ---------- Previous post was at 15:15 ----------
Alpha 100319:
orbides.1gb.ru/orbf/uap-alpha-100319.zip
Changes:
-Grand optimization of Sync Orbits AP
-More careful plane aligning, should use one node most of the times
-Added wait for other vessel's sequence completion in vessel tool
-Added heading to trans-orbital
-Added undocking tool
-Added status string
-Fixed state of sequence running save
Bugfixes and optimizations.
The Sync orbits should now be much more consistent and precise, selecting the manoeuvres better.
Align planes should take one node most of the time on small changes, so Martian chase now completes within one orbit, Sync+Align.
These two are the targets of this alpha, as well as any bugs.
What next?
-Moon to Earth?
-Into the big interplanetary void?
-Landings and re-entries?
-OrbitHanger?
Last edited: