Soldia

Can confirm. When replaying the track, Jester menu is sticked open. Haven't found a solution to this unfortunately

1. No FC3 Plane (Tried it with Mig-21 and A-10C so far) 2. WH (with Generic Pedals but I don't think that's a factor) 3. It's whenever I build the script from CTS UI and then either start vom CTS UI or compiling directly in Target As I said, doesn't seem to be a FC3-specific behavior. All variables in the constants block (see below) are defined after that block. I've attached the complete DCS_World.tmc

Thank you Home Fries for the great work. I currently got an issue (being on latest version 2.26, Target at v3.0.18.328 v2, Warthog Stick and Throttle) while compiling. I haven't found any useful information on that particular issue. When compiling, I got the following error: Compile Error:Symbol not found: Eng_Start_FC3 in DCS_World.tmc at line 147 Looking at the generated DCS_World.tmc file, there is of course the corresponding line 147 and line 644 (for me) where that variable is set / used: 145 int WH_SC_SetRange=0; 146 int SPU9_BS2=1; 147: int Eng_Start_Su27=Eng_Start_FC3; 148 int Swap_UR_MicSw=1; 149 int UR_ER=TS3_ExtRadio_Keys; ... 642 int Eng_Stop_FC3=5000; 643 int Eng_Start_A10A=60000; 644: int Eng_Start_FC3=10000; So, the definition of Eng_Start_FC3 happens after using it. Moving line 644 before 147 solves that issue, but other issues occur (same same but different -> Variables are used before they are initialized). TL;DR: When building the script there are several issues with code order for me. I don't know if there's anything I can do or if anyone else encountered that. If you need more information, please let me know. Thanks

Got that one once, too. Until now it never occured again. Are you able to reproduce it?