John Dowson

I have checked this and it is correct, i.e. it contains the 1.0.6 WASM. Your issue is that you have the 1.0.5 WASM installed. If using FSUIPC7, you should download and install the latest release (and maybe also try/install the 7.5.0-beta available in the Announcements sub-forum), If not using FSUIPC7, then install the WASM from the FSUIPC WASM module zip file that you downloaded.

That log is not using the version posted above, it is using 7.4.18 (the current released version). Also, you haven't set InitialStallTime=-10 : or maybe you set this but it was reverted as you were using the wrong version.

Did you also extract/install the WASM folder (fsuipc-lvar-module) from that zip file to your Community folder? if not, please do that and try again. That message indicates that the dll is the correct one for 1.0.6, but you have the 1.0.5 WASM module installed. If you have already done that, then I will check the version.... John

👍

For such events that are constantly logged, you should ignore these by setting the DontLogThese ini parameter. See the Advanced User guide for details. In the assignments panel. check the Select for Preset checkbox. Then the Find Preset... button to see the tree-preset selection box. I do supply user manuals...read them! John

Then please use the specific support forum for FSUIPC7 / MSFS. I will move your post. Have you tried the available presets - FNX320_LIGHT_RWY_TURNOFF_ON, FNX320_LIGHT_RWY_TURNOFF_OFF or FNX320_LIGHT_RWY_TURNOFF_TOGGLE?

What FS are you using, and what version of FSUIPC? Have you tried activating logging for Events, open the logging console and see what is logged when you turn on/off the runway lights in the VC?

Ok, thanks for the update.

No, that is not the WASM module, it is the persistent storage area for the WASM, which in MSFS2020 was under C:\Users\[USERNAME]\AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module If using FSUIPC7 with MSFS2024. please use the latest beta, available here: All questions / comments / requests on using FSUIPC7 with MSFS2024 should be posted in that topic for the time being. I am closing / locking this topic now. John

If things are working, then you can just leave everything as it is. However, please update to use JoyLetters - just set AutoAssignLetters=Yes in the [JoyNames] section of your ini. If you want to try cleaning the registry, follow the instructions previously posted. But switched to JoyLetters first, and run P3D/FSUIPC at least once after doing this, to get your files updated to use the letters.

By the way, you are now getting two devices reported with the same GUID (previously was 3): Maybe make sure those two devices (vJoy Device and Flight Throttle Quadrant) are connected to ports on different USB hubs. GUIDs should be unique for each device - I don't understand why these are being reported as the same. You should really be getting unique GUIDs from HID scanning. Cleaning the registry won't correct this.

That is surprising as your log shows two devices assigned the same id and have the same GUID: Are these two devices working ok? I would do this as your registry is still a mess. Maybe also check that you have USB3 devices plugged into USB3 ports, and USB2 devices connected to USB2 ports.

What do you mean by 'lost many of my device'? You should not try and do anything with any device yet. As O said, just run and exit and show me the files. Restore what from backup? Restoring the registry dump from back-up should put your system/registry in exactly the same state as it was before you ran the .reg script, This is the whole point of taking a back-up... That script only removes the registry entries for 4 devices and in no way should affect your USB ports/hubs, Sorry but I have no idea what you did or why this is happening. You obviously have not followed my instructions, or I would have expected to see your files after you had ran P3D/FSUIPC for the first time after cleaning the registry and reconnecting, and before doing anything else. Sorry, but I cannot help if you are now having issues with USB controllers - this is nothing to do with FSUIPC.

Ah, ok.

I don't think you can open that file in MSFS2024....if you succeed, let me know!

The path is available at offset 0x3C00. FSUIPC gets this from the AircraftLoaded event.

FSUIPC tries to read the icao_type_designator, icao_manufacturer, icao_model & icao_airline from the reported location of the aircraft.cfg file. However, it can only do this if the file is readable and not encrypted. Are you sure FSUIPC is reading this? Check offsets 0x0618, 0x09D2 and 0x0B26 and you will probably see that they are empty, which means that the aircraft.cfg can't be read.

Some devices do report multiple GUIDs - I wouldn't worry about this. Yes you should, and you should not have to reconfigure anything. It would be a lot easier to fix your current issue if you had done this, but probably not a good idea to do this at the moment - we can do this later. Can you do the following please: - run the windows registry editor and take a back-up of your registry - disconnect the following devices: MJ162, MJOY32, VKB-Sim Space Gunfighter L, Flight Throttle Quadrant - download and run (i.e. double-click it) the attached .reg file: removeDevices.reg - reboot your system - reconnect the devices you disconnected - run P3D/FSUIPC, and once loaded just exit - show me / attach those 3 files again (ini. log and JoyScan.csv). Do NOT change anything or assign/re-assign until we have corrected this. - if you can, let me know which device ids have changed from those used for your assignments, i.e. if you previously assigned to the device when it had a different id, let me know the current id and the id that was previously used for assignments on this device Note also that your ini file is a bit of a mess. The '//' characters are NOT the comment string for ini files, although such lines will be ignored. Best to remove these or replace with the comment character ';' (a semi-colon). You should also consider using substrings for your profile aircraft names, e.g. for the FSL320 profile, change to You should do similar changes (i.e. use substrings to match all variants) to all your profiles. Please also update to the latest and only supported version of FSUIPC6, v6,2,1. John

I have now released 7.5.0a-beta. Please see Please use that topic for all questions/issues/feedback - I will lock/close this topic now. John

I have now released 7.5.0a-beta. Please see If you downloaded this version from this topic (previously available above) then please download this new version as there have been some changes. The version number is the same (7.5.0a), but the build date for this official beta release is now 21st November (previous version was 20th December). I am closing/locking this topic now. Please use that Announcements topic for all issues and feedback with this version. John

...and one thing I don't understand is that 3 of your devices have been assigned the same GUID: GUIDs should be unique....I don't understand why these aren't. Please reboot before providing me the files.

There is no point doing this...the entries associated to a JoyId number will be completely re-written by FSUIPC. You should also use/enable JoyLetters to prevent issues when the JoyIds changer. Its also not a good idea to disconnect and reconnect devices when P3D/FSUIPC is running, especially if you have issues and are not using JoyLetters. Do you still have your original FSUIPC6.ini? If so, please use that, otherwise use the latest one which has all your assignments. Start P3D/FSUIPC, let it load and then exit. Then show me / attach the files FSUIPC6.log, FSUIPC6.ini and FSUIPC6.JoyScan.csv files - I need to see all 3 from the same session. The JoyScan file you attached shows that your registry is a bit of a mess and will need cleaning. I can provide a script to do this once I have seem those files. From that file, it looks like you have the following devices: 1 vJoy devoce 1 TCA Q-Eng 1&2 2 MJ162 2 MJOY32 1 Logitech G27 Racing Wheel 1 VKB-Sim Space Gunfighter 1 Flight Throttle Quadrant Is that correct?

That is just returning the value of the simvar FUELSYSTEM PUMP SWITCH at index 2. In FSUIPC, that value can be found in offset 0x0B05, but only when you have set the ini parameter NumberOfPumps to a value > 1. In general, it will depend on the output preset definition on how you would read the value in FSUIPC (and FSUIPC clients). For simvars (or A-type variables), you can check to see if it is already in an offset and use that if so, otherwise you can add any simvar to a spare/free FSUIPC offset for both read/write. See the Advanced User guide on how to do this. Yes, that is all that calc code does. John

I haven't got time now to do a proper beta release, will do this tomorrow. but for now can you try the attached version, which is 7.5.0a. This is for both MSFS2020 and MSFS2024. I wo; release this in the Announcements sub-forum tomorrow. John

Hi Umberto, Yes - this will be updated and the version number for MSFS2024 will be 14. However, it will now only be populated once connected to the FS. Note you can also use offset 0x3124 which holds 110 for MSFS2020 and 120 for MSFS2024. I will be releasing a beta version of FSUIPC7 for MSFS2024 compatibility shortly. John