kaha

I didn't realize it because I was using an aircraft from the store.

I found the cause. Somehow my Community content got disabled.

I don't know how to check that. I rebooted and emptied the Community folder (except the fsuipc module). To no avail. I don't know a way to verify files for the store version.

I un- and then reinstalled FSUIPC but it's still not working in MSFS2024. What can I do? All my axis concerning throttle, prop, mixture, spoilers, etc. rely on auto scripts, also all my Arduinos. The problem started yesterday afternoon, shortly before the SU2 update was live. I probably used MSFS2024 while the SU2 update went live. Only on the next start of 2024 I got the update. Here's the screenshot of my SU2 update, timestamp 17:03. Now please check the timestamp of the 2024 log file in my screenshot 2077, that was the last log with timestamp 15:42 SU2 Update.zip

That wasn't me.

Thank you for the explanation. The FSUIPC WASM module isn't in the list.

Hmm.. strange... "List Lvars" does nothing. And "Reload and List Lvars" also does nothing.

This?

How can I check that?

But there's nothing.

Do you also have MSFS2020 installed?

I now deleted all FSUIPC_WASM.log files on my system. Then I ran MSFS2024. auto lua scripts did not start. There is no FSUIPC_WASM.log file to find. I assume it should be in this folder?

I just saw the folder names in the search for E: and F: got truncated. Here's a better version. Screenshots.zip

John, there is no FSUIPC_WASM.log file for MSFS2024. I only could find log files for 2020. Attached are 3 screenshots of a file search for the log file on C:, E: and F: MSFS2020 is on F:, MSFS2024 is on E: Also attached is the FSUIPC_WASM.ini file for 2024 as I changed it to log level DEBUG. THis file is in folder E:\MSFS2024\Community\fsuipc-lvar-module I changed the value for DetectToConnectDelayAut, thank you for the hint. FSUIPC_WASM_ini.zip Screenshots.zip

Since today my Lua scripts I have in the [AUTO] section of the .ini file don't run in MSFS2024. In MSFS2020 it works. I have one single FSUIPC installation for both sims. Attached is the .ini file and both logs (2020 and 2024). What can possibly cause this? I think MSFS2024 must be the cause because I didn't change anything in FSUIPC and it worked in 2024 this morning but not this afternoon. Karl FSUIPC7.zip

Thank you, John! Karl

Unfortunately this doesn't work out. It depends if the ATC Type in the aircraft.cfg file has been set correctly. Just 3 examples: AH's Cessna 170: "C170BT" Miltech's Chinook: "$$:Helicopter" Microsoft's Bell 47J: "Bell"

Thank you, I'll try that.

Maybe I missed something in the documentation? Karl

John, you're of course right. For my peripherals I use FSUIPC exclusively. I cleared all my MSFS profiles (except keyboard and mouse) but somehow MSFS 2024 managed to come up with a standard profile for the flaps. Works now. Thank you, Karl

Ok, I'll check. Thank you. Karl

Here we are. For this test I used the same FSUIPC installation as I use for MSFS 2020, Karl FSUIPC751.zip

I use the binding in the screenshot. This works in 2020, but in 2024 it extends and retracts the flaps completely. Anyone also sees this? Tested with empty Community folder and with 2024-native aircraft as well as with 3rd party aircraft. Not sure what I'm doing wrong here. Karl

Thank you!