Cockpit persistence
-
Hi,
Will Cockpit persistence feature be launched in the future? Not only the radios and fuel, but also all switch and lever positions? -
Hi,
Will Cockpit persistence feature be launched in the future? Not only the radios and fuel, but also all switch and lever positions?@WinterMelon if you use AAO and care for some custom solution beyond what may be possible in the simulator, you can have a look at my templates for the Duke, which also implement extended per-livery state saving, optionally including aircraft position.
See README file in theaao/folder.
https://gitlab.com/randolf.lemmont/fs-bksq-duke-mods -
@WinterMelon if you use AAO and care for some custom solution beyond what may be possible in the simulator, you can have a look at my templates for the Duke, which also implement extended per-livery state saving, optionally including aircraft position.
See README file in theaao/folder.
https://gitlab.com/randolf.lemmont/fs-bksq-duke-mods -
@Randolf
Thank you so much for this solution. Works like a charm (I use the scripts assigned to voice-commands).Only the load position does not work but I have to figure this out.
-
@Randolf
Thank you so much for this solution. Works like a charm (I use the scripts assigned to voice-commands).Only the load position does not work but I have to figure this out.
@syff when you look at the script
Duke / StateLoadPosition
and change this line near the top
(NUMARR:StateSaveValues) next 1 != if{ (GOTO:end) } \nto this:
(NUMARR:StateSaveValues) next 1 < if{ (GOTO:end) } \nposition loading should start working.
Will make a new release version of the template soon, after testing it. -
@Randolf
Thank you so much for this solution. Works like a charm (I use the scripts assigned to voice-commands).Only the load position does not work but I have to figure this out.
-
While applaudable, this solution is not helping those of us who wish for extended native support without the need for additional applications
They usually only bring further complexity, risks, problems and sometimes costs.When I left FSX behind, I was so happy that I no longer needed to run so many external applications and 'maintain' so much to keep my simulator running. I'm not a technophobe but I have less time than when I was a student or bachelor some 20 years ago, with endless computing hours to tinker.
To that end, feel free to add your wishes to the Feature Requests thread. It can't hurt!
-
While applaudable, this solution is not helping those of us who wish for extended native support without the need for additional applications
They usually only bring further complexity, risks, problems and sometimes costs.When I left FSX behind, I was so happy that I no longer needed to run so many external applications and 'maintain' so much to keep my simulator running. I'm not a technophobe but I have less time than when I was a student or bachelor some 20 years ago, with endless computing hours to tinker.
To that end, feel free to add your wishes to the Feature Requests thread. It can't hurt!
@Mustang I totally understand your position. It would be so cool if MSFS would be able to do at least half of what is possible with external control programs like AAO or FSUIPC. But that's just not the reality. And I think, and it's just my opinion, or how I like to do things, that in current status of the simulator, it's necessary to have an external program to control complex aircraft, like the Duke and similar, to the level I'd want, with my hardware controls. And I really enjoy the freedom and degree of control this solution gives me.
But as I said, I'd really wish the simulator did a better job at this, and if there is anything that can be done by aircraft addon developers to ease this situation, go for it. But I'd also like addon developers to focus their efforts on things that are not already solved by other means. -
@syff it's fixed in the new release, plus more values saved. State loading should be able to load previous versions of the save file.
https://gitlab.com/randolf.lemmont/fs-bksq-duke-mods/-/releases
