more state-saving items
-
Hello,
After my first hours on the Baron I have noticed a few switches that I'd really love state saving for.
Generally, I'd love a full state saving like some other developers offer, although I understand you are not doing that currently.
The things I'd like to see saved are the following:
-Audio Panel Settings
-QNH Setting
-Decision Height
-Circuit BreakersThere's no "correct" position for those and therefore Iove to see them saved.
It's just nice seeing the last QNH you had on the last flight. Also it's pretty annoying to have to select the audio every time you load the aircraft - You'd just leave that on.
But the thing that really annoys me the most is - the DH
I only fly VFR and therefore I'd never select 200 - I'd have either 400, 500 or 1000 - and I'd really love not having to set that every single time.I can very well live with a selective state saving, as most of the switches are going to be in the same position anyway (if you follow your procedures) - but those few have to be changed every single flight, that's why I find them a bit annoying.
Kind regards,
Jannik -
I wanted to add a few state-saving items to Starship for the same reason. In the end, I implemented a StreamDeck button that fires an Axes & Ohs macro. The macro hits the LVars to set things to how I’d leave the plane - com2 audio on, tuned to 121.5 (guard), and a couple others.
In Starship, I located the state saving & restoration code, but my attempts to add more items wasn’t successful. Hence the AAO macro.
-
I wanted to add a few state-saving items to Starship for the same reason. In the end, I implemented a StreamDeck button that fires an Axes & Ohs macro. The macro hits the LVars to set things to how I’d leave the plane - com2 audio on, tuned to 121.5 (guard), and a couple others.
In Starship, I located the state saving & restoration code, but my attempts to add more items wasn’t successful. Hence the AAO macro.
@MarkS I don’t have any tools like that unfortunately.
