- Joined
- Dec 25, 2010
- Messages
- 46
- Reaction score
- 0
- Points
- 0
Am I correct in concluding that the reason the autopilot acts like a drunken monkey with something heavy docked, is a mass issue as well as a COG issue?
I've used ShiftCG() or SetThrusterRef() to center the RCS arrays around the COG, however, even with something (heavy) docked along the centerline, 'prograde' still swings wildly about.
I'm new to coding for Orbiter but the autopilot is acting like it's expecting a certain amount of angular acceleration from the thrusters to slow down and is overshooting the mark.
I've also noticed that GetEmptyMass() doesn't change when a ship docks, so am thinking this is the problem.
Wouldn't using SetEmptyMass, without zeroing out the docked ships, just add more 'real' mass and not solve the issue?
Is there a way to extend the default autopilot functions, or has anyone tried doing so via memory hooks?
Or am I completely off base here?
I've used ShiftCG() or SetThrusterRef() to center the RCS arrays around the COG, however, even with something (heavy) docked along the centerline, 'prograde' still swings wildly about.
I'm new to coding for Orbiter but the autopilot is acting like it's expecting a certain amount of angular acceleration from the thrusters to slow down and is overshooting the mark.
I've also noticed that GetEmptyMass() doesn't change when a ship docks, so am thinking this is the problem.
Wouldn't using SetEmptyMass, without zeroing out the docked ships, just add more 'real' mass and not solve the issue?
Is there a way to extend the default autopilot functions, or has anyone tried doing so via memory hooks?
Or am I completely off base here?