ninguru

Yes, I have tested that in various ways too. I also tried inserting a longer split, but there is no response unless I set (A:CAMERA STATE, Enum) first. However, if I set (A:CAMERA STATE, Enum) first, then some kind of internal stack seems to take priority. From here on it’s just my personal speculation: for example, when you press Ctrl+4 twice, it returns to the previous view. At that moment, the previous view must be stored somewhere in a stack, and when moving from the previous view to the next (or returning), the simulator plays out a smooth transition animation. Because of this mechanism, there seem to be two states — the “previous view” and the “next view.” I suspect that this mechanism is internally programmed to avoid directly setting the previous view, in order to preserve that transition behavior.

Lorby_SI, Afterwards I found out on the MSFS DevSupport page that this issue has already been registered in the bug tracking system: https://devsupport.flightsimulator.com/t/camera-reset-events-and-variables-dont-appear-to-work/11444/4 In any case, what I wanted was to always switch to the cockpit pilot view, no matter which view mode I was currently in. I was struggling with why the following sequence did not reliably set the pilot view: 2 (>A:CAMERA STATE, Enum) 1 (>A:CAMERA SUBSTATE, Enum) 1 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 1 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum) But it seems everything is resolved (at least for now) by adding 1 (>A:CAMERA REQUEST ACTION, Enum) as the first line. Setting this line by itself appears to have the effect of force-resetting everything except (A:CAMERA STATE, Enum). You may have already known this, but I wanted to report back. Thanks!

Thank you very much for your quick reply, Lorby_SI. For the time being, I will try to use the virtual keyboard to implement this and assign it to my controller. Thanks again for your support!

Why is it that returning to the original cockpit view is sometimes refused? For example: (2,1,1,1) → (2,5,2,0) → (2,1,1,1) does not work (2,1,1,1) → (2,5,2,0) → (2,1,1,0) works (2,1,1,0) → (2,5,2,0) → (2,1,1,0) does not work (2,1,1,0) → (2,5,2,0) → (2,1,1,1) works Even when I build a script, I keep running into this problem. Could you explain why this happens? I am monitoring the SimVars directly, so I can confirm the values change exactly as shown above.