Global throttle limiters cause issues between ascent autopilot and landing autpilot, node executor, etc behavior
sarbian opened this issue · 4 comments
As said in the tittle.
"I guess it could just dot the surface relative velocity with the thrust vector and only throttle down if positive, or even use the sign of the dot to decide which way to throttle so it will automatically use the engine to brake when above max Q�"
Limit Q rather needs a dedicated check if you're burning retro, because it can fatally interfere with emergency braking, as in that you realize your re-entry is literally too hot and you fire the engines and nothing happens.
Took me an hour and several retries until I realized that this little fucker constantly locked the engines up because I was obviously going way too fast, take a guess why I WANTED to fire the engines, but it locked them up : /
In general, the throttle limiters seem to cause a lot of issues by users that set the up on ascent and then forget they're set and they kick in other times.
#1229 is probably related