Hi,
I have written a TARGET script for my WARTHOG HOTAS which uses some state tracking.
I have noticed that some system states are carried across a menu log or restart and some are not which can cause some of my TARGET state flags to become misaligned.
Would it be possible please to ensure once the game is loaded most of the various ship systems states return to last known state (where it would make sense).
Example of current state resets that do not make sense (to me);
1) If your HUD is in analysis mode, it gets reset to Combat mode
2) If your lights are on, they get reset to off
3) If your cargo scoop is deployed, it gets reset to retracted
4) If your hardpoints are deployed, they come back retracted
5) Reverse thrust (if set to toggle in bindings) is reset
6) Wing Beacon is reset to off. This one only makes sense if I start in Solo mode but should be carried over when restarting in PG or Open.
States reset that do make sense (to me);
1) Silent running is reset to off (this can stay as is thanks!)
2) Supercruise is reset to normal flight (this can stay as well)
Example of states carried across a restart/menu log;
1) Flight assist off (strange, but ok)
2) Report Crimes against me retains it's state (as it should)
With the status.json in the ED Journal folder, I can at least programmatically check some of these and set/reset as required in my scripts.
Others though, I cannot.
It'd be great if there's some consistency with carried over states, or alternately, include everything that can be toggled on/off within status.json.
Thanks for your consideration.
Clicker
I have written a TARGET script for my WARTHOG HOTAS which uses some state tracking.
I have noticed that some system states are carried across a menu log or restart and some are not which can cause some of my TARGET state flags to become misaligned.
Would it be possible please to ensure once the game is loaded most of the various ship systems states return to last known state (where it would make sense).
Example of current state resets that do not make sense (to me);
1) If your HUD is in analysis mode, it gets reset to Combat mode
2) If your lights are on, they get reset to off
3) If your cargo scoop is deployed, it gets reset to retracted
4) If your hardpoints are deployed, they come back retracted
5) Reverse thrust (if set to toggle in bindings) is reset
6) Wing Beacon is reset to off. This one only makes sense if I start in Solo mode but should be carried over when restarting in PG or Open.
States reset that do make sense (to me);
1) Silent running is reset to off (this can stay as is thanks!)
2) Supercruise is reset to normal flight (this can stay as well)
Example of states carried across a restart/menu log;
1) Flight assist off (strange, but ok)
2) Report Crimes against me retains it's state (as it should)
With the status.json in the ED Journal folder, I can at least programmatically check some of these and set/reset as required in my scripts.
Others though, I cannot.
It'd be great if there's some consistency with carried over states, or alternately, include everything that can be toggled on/off within status.json.
Thanks for your consideration.
Clicker
