John Dowson

I didn't know that could be disabled...! Can you re-enable it and test again then?

In steam, you can verify the integrity of the game files of the MSFS2024 installation. Can you do this with the MS Store version? If so, try that.

Sorry but I have no idea why MSFS2024 is not starting the WASM. Are all your other WASMS being loaded? Did you reboot? Try temporarily moving everything out of your MSFS2024 Community folder except for the FSUIPC WASM module - does it then load/start? You can try reporting this on the Asobo forums as there is nothing I can do or advise if MSFS2024 is not starting the WASM.

Ah, sorry - didn't notice that was from another user.

So the WASM is being registered but not mounted and initialized. I have no idea why this is. It must have ran at some point as you said: So something must have changed. Try re-installing FSUIPC7 (and the WASM).

Then it isn't running. I have no idea why this is. Check the logging console (Debug-Console) and search for fsuipc and see what messages you see.

I have looked into this further and it looks like the default keys to change the views have changed. By default: - quickview left/right are now on shift + h/f and no default for up/down (MSFS2020 uses LCtrl + Up/Down/Left/Right) - look on shift + k/l/j/i (MSFS2020 uses LShift + Up/Down/Left/Right) - translate on shift + s/w/a/d (MSFS2020 uses Up/Down/Left/Right) So, to use the same keys as MSFS2020, you would need to map the keyboard controls to use the same keys as MSFS2020. Alternatively, you would need a separate installation for MSFS2024 and map the hat buttons to the default keys to control the views in MSFS2024. Using the view controls directly still doesn't work.

View control has always been difficult in MSFS2020/2024 as the default view controls don't seem to work. I have my hat switches assigned to the default keystrokes to control the view (pan, eyepont and quick-view) which works ok in MSFS2020, but in MSFS2024 they only seem to control the panning and not the eyepoint or quick view controls. No idea why. I will look into this further in MSFS2024 when I get a chance. John

This image shows the WASM running (note status is READY)::

You have to enable devmode in MSFS in the Advanced options, then use the Debug->Display WASM debug window, then select the FSUIPC WASM lvar module and then look in the Module section tab. That is because FSUIPC isn't receiving anything from the WASM. You said that your lua scripts were started earlier, so this means the WASM was running and working at some point. I have no idea why it is no longer working. Try rebooting and try again.

As I said, your previous screenshot showed those files...if the log file is not now being created, then the WASM isn't running. Check in MSFS if the WASM is actually running.

As I said, your previous screenshots showed the log files. You are looking in the wrong place - for MS store installs in MSFS2024, it should be under AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvarmodule\work as I said....please see the documentation that I previously referenced... Yes, of course. But I have steam installations, not MS Store.

I can't tell anything by looking at your files as I have no idea when you tried to operate the trim/ When you operate the elevator trim, what macro name do you see logged in the PFChid64.log file? What controls do you see logged in the FSUIPC6.log file? Note that you need to activate logging for Events (non-axis controls), which it looks like you haven't done. Also, open the logging console and you will be able to see what is logged when you activate the trim. That is the calibration used when the elevator trim is assigned to an axis in FSUIPC and is probably not used. Those values look very strange anyway (and the format is wrong) so I would remove that. You would normally calibrate the elevator trim on page 6 of the calibration screens and not modify the ini entry directly. But this only applies to the elevator trim axis. Does your device have a trim wheel or buttons/a rocker? If a wheel, does this use buttons or is it an axis?

There must be - that location was for steam installs - for MS Store installs it should be under: AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvarmodule\work In fact, your screenshots show you have one in that location. Screenshot (2077).png shows the log file for MSFS2024. and Screenshot (2076).png shows the log files for both 2020 and 2024. There won't be an FSUIPC_WASM.ini file there by default - you have to copy this across from the Community folder. See the section WASM module ini file and parameters on page 51 of the Advanced User guide for details on file locations. You can also set Debug level logging there. Note that that file gets overwritten when you re-install/update, which is why it is better to change the one under your AppData folder, which also takes precedence (when provided). Ok, then no need to send/show me the WASM log file then. Keep Debug level logging activated, and the next time they don't start show me the WASM log file. John

I just tried MSFS2024 here and it seems ok, so I will need to see your FSUIPC_WASM.log for MSFS2024. Should be located under: AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc-lvar-module\work You can set Debug level logging in the FSUIPC_WASM.ini file in the same location. John