John Dowson

Ok, thanks. John

No, no point. This is nothing to do with FSUIPC if your devices are controlled by the Cpflight plugin. Has that been updated yet for MSFS2024? I only support FSUIPC, not CPFlight. John

Are you using the latest beta of FSUIPC7 which has added support for MSFS2024? If not, please update to that version. See If using that version, please post any issues in that topic until I release this version officially, and make sure to at least include/attach your FSUIPC7.log file. John

Could someone who has an MS Store install of MSFS2024 please let me know where the WASM persistent storage area is for this version, i.e. where your FSUIPC_WASM.log file is located. Is it under: AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvar-module\work or maybe under AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\WASM\MSFS2020\fsuipc-lvar-module\work ?

Yes, as these devices are not assigned in FSUPC, in fact you have no assignments at all, it cannot be anything to do with FSUIPC. Your MCP and Efis are not even detected by FSUIPC. The log file you attached when FSUIPC7 was running and ends after 3-4 seconds and shows nothing. Please ALWAYS exit FSUIPC before attaching any files. John

¿Puedes decirme cuál es el error? Además, adjunta tu archivo FSUIPC7.log. ¿Estás usando un add-on para el StreamDeck? Si es así, comprueba que se haya actualizado para MSFS2024. Consulta:

No need for a screenshot. This sounds like your device has gone to sleep (as the button press is not recognised) - check the USB hub properties in device manager. Otherwise, please show me those files with the logging activated.

Both log files look ok and show that FSUIPC7 was running and had not crashed. When this occurs, can you operate in the FSUIPC7 main window? i.e. does Alt+F open the main window, and can you then open the assignments windows and use those? If so, can you see the assignments you have bound to the switch? Is the switch/button recognised? The WASM log looks ok, and shows that that didn't crash. You do have a few reconnection attempts at start-up, although this is nothing to do with the issue you are having, To prevent these, can you please set/update to the following in your FSUIPC7.ini (in the [General] section): DetectToConnectDelayAuto=90 InitialStallTime=45 StartUpTuningDoneVersion=-1 For your issue, can you please activate logging for Buttons & Keys, Events, Extras and WAPI Debug level logging, and the next time this occurs first open FSUIPC7 and the assignments window and press the button (presumably not recognised?), then exit FSUIPC7 and send me/attach your FSUIPC7.log and FSUIPC7.ini files. Then restart FSUIPC7 and try again. Does it now work? Presume so (from what you said), but if not, please then exit MSFS and show me / attach your FSUIPC_WASM.log file. Also please check the power settings on your USB devices and hubs, and make sure Allow the computer to turn off this device to save power (under Power Management) is disabled. Windows has a habit of resetting this setting for some reason... - John

Yes, you will need to purchase a license for FSUIPC6 for P3Dv5 (and it is also valid for P3Dv4 and P3Db6). Your WideFS7 key is still valid and this can be used with FSUIPC6. John

If you have previously purchased a license for FSUIPC6, then the details of your purchase (including the license key) will be available from your SimMarket account. If you don't have a license, you can purchase one from SimMarket. John

The trial license has been updated, now valid until 01/01/2025, John

And are they working or not? And is your issue with FSUIPC or with MSFS2024? If everything still works in MSFS2020 but not in MSFS2024, I would suspect that the issue is due to changes in MSFS2024, and such issues I will investigate later (and maybe better to raise a separate topic for this). If its no longer working in MSFS2020 with this version and previously was, then I need further details. Basically I want to confirm this version is working as usual in msfs2020, and any specific issues for MSFS2024 (not working, and previously working in MSFS2020) I will investigate further, but after I have officially released 7.5.0. I already have several issues that I need to investigate further and most probably report to Asobo. But such details take time and won't hold-up the release. John

The problem when doing this is that many browsers cache the download, so if i use the same name for different versions, when people download it downloads the older cached version rather than the latest. So I won't be changing this for the time being. Hopefully c-5 will be the last beta and I would like to release this in a few days anyway. If no or only minor errors reported in the next couple of days, I will release on Wednesday 4th. John

First, there is no point in monitoring such offsets, Monitoring logs the value of the read offset, whereas you write to the write offset (there are separate areas for read and writing), Well, no point in monitoring, and even if you did you should monitor as a FLT64. The parameter/value for all input events is a 64-bit floating point value (double), as it is for lvars, So make sure you write it as such, and not as an S32 (int). Please re-read the documentation.... John

No. Please see the FSUIPC7 Offset Status document on how to use the facility at offset 0x7C50: John

I am not sure why this would be - I will take a look sometime next week.

I have updated the installer to v5. The only change is to the splash image displayed when starting MSFS2024. Hopefully this while be the final update for the time being... John

There are no id numbers associated to Input Events. Each one is identified internally (and by MSFS) by a hash number, but I don't make these available. But to send an Input Event via an offset, you should use offset 0x7C50/0x7C90 not 0x3110/0x3114, and use the input event name, preceded by 'I:'. John

Which would confirm that it is not related to FSUIPC, but more of a coincidence that it also happens when FSUIPC is loaded. I think this issue has been reported before, but I can't remember what the issue was caused by, sorry.

Your log shows you didn't install the WASM for MSFS2024, which could be an issue, Anyway, 7.5.0c has been released now with a full installer, so please download and re-install from John

So you have an MS Store version of MSFS2020 and a steam version of MSFS2024? Thats what the installer detected, but from that message it looks like the start icon was installed for a MS Store version for MSFS2024. Just checked this and found the problem. I will upload a new version shortly. The Community folder for your MSFS2024 version is also rather strange as it is under another Community folder: CommunityFolderLocation=G:\SteamLibrary\steamapps\common\Limitless\Community\Community\ Is this correct? Later: @Rotorfib please download the latest update and try again

Different (final) paths are now used depending on what is installed - can be under ...\FSUIPC7 (when installed for 2020), ...\FSUIPC72024 (when installed for 2024) or FSUIPC7Both (when installed for both at the same time)..

But you shouldn't need to do this. If you selected to install in MSFS2024, the installer should have installed the WASM folder to the 2024 community folder. Ah, then please update and try again. Is this in MSFS2024, MSFS2020 or both? Was it previously working in MSFS2020?

Oops...that one broke Steam... updated again.

Found an issue where it wasn't showing the MSFS versions selections page for MS installs. I have corrected and uploaded an update. @ksp100, @danastasiou & @Doc_Z can you please download and try again.