F-WWOW

Thank you so much John for your prompt, usefull and teaching answer! 👍 I will look at that this week-end and come back to confirm the resolution... or not 😉

Hello everyone! First of all, I am a newbie in programming and I don't understand all logics explained in the documents. Sorry for that. I am extracting the Ifly 737 MAX Lvars from the WASM file to put them in the events.txt file. If I success on most of the commands, I encouter an issue with the external lights. For example, I assign a joytick button to change the Logo lights switch via these commands: Logo_Light_SW_ON#10 (>L:VC_Logo_Light_SW_VAL) Logo_Light_SW_OFF#0 (>L:VC_Logo_Light_SW_VAL) All is OK with the switch position but no effect on the external lights excepted by clicking on the switch. I have seen that a "Logo_Light_Display_VAL" exists but I could not find how to modify its state. My other question is how to toggle a switch with values 0 and 10? And my last one: where to find a tutorial for the events.txt syntax? Thanks in advance for your help.

Found the solution. Just have to delete the [PMDG] data at the end of the Autosave*.fxml file, load the saved flight in P3D, and then the associated PMDG panelstate file manually.

Hello all! I am using the latest version of FSUIPC (4.937) with P3D 2.4 and often flying with the PMDG MD11. Autosave is activated but each time I load any of the 10 autosaved flights, P3D loads my startup situation with the default aircraft (Beech Baron) lined up on the runway instead of the saved flight conditions and panel state. Very shortly after the situation loaded, I have a CTD with atc.dll. I read the autosave*.xml file and all data seem to be correct (name of the aircraft, conditions, etc...). Any idea?