Similar MSFS 2020 issue: A: Camera Statee does not ever take a value of 32 in MSFS 2020.
**Bug description:**This is a SimVar issue, so it does not affect just one package/panel. It has been tested with the TDS GTNXi Pro. When in flight and pressing ESC, then Resume Flight, the A:Camera State SinVar gets set to 32 for a brief period of time, but we do not get to the main menu.
Repro steps: Enter in flight, monitor the SimVar A: Camera State. Press ESC button, then resume the flight. For a brief second the value of 32 is being written right after pressing the Resume button, while the main menu, of course, is not loaded. This is incorrect and we should receive value of 32 only when in the main menu.
As far as we can deduce, value of 32 is the main menu?
In addition, the MSFS 2024 SDK does not mention camera states higher than 25, while MSFS 2024 has values up to 35-36 at the time of writing and we have no clue what they are.
I don’t think this is a bug - the documentation for the Camera State simvar says:
Note that not ALL possible enum values are shown, since some values are internal only, and some values will do nothing, but have been reserved for future expansion of the camera system.
Thank you for your input to this. I have analyzing the SDK text as well prior to posting this bug report.
In this case, I do not think that value 32 of Camera State is an intermediary state that should be ignored, but rather value 32 is a (yet undocumented) value of Main Menu.
Hence why if you monitor the SimVars using SimVarWatcher, as soon as MSFS 2024 loads and you are in the Main Menu, only value 32 is displayed for the duration of staying in the main menu.
Hence why value of 32 should not display, for a brief second, when resuming the flight, but not going anywhere near the main menu.
This can be also confirmed from the findings in this post:
Yes, I can see this now. This is also an issue for my app, as I also rely on the camera state reaching the main menu (15).. In my code I preciously also had a check on camera state of 32 for MSFS2024 as I think this was also needed, but I removed that as it was also going through this state in other situations (on reload flight I think) which was causing my app to think it was going back to the main menu.
I agree this is a serious issue that should be addressed ASAP.
…but I think the currently documented camera state of 15 should be used for the main menu, not adding 32 as another main menu state. I don’t mind it going through this state on reload/resume flight, or when going back to the main menu, but it should be 15 when at the main menu.