John Dowson

That is wrong - for Steam installs, its under: AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc-lvar-module\work The folder will only be there if you are using the FSUIPC WASM module. Ok, I didn't realize it was 2024 only... Well, its the FSUIPC_WASM.log file that I need to see, and attached only once MSFS2024 has exited.

This is an MSFS issue and nothing to do with FSUIPC. You should use the MSFS/Asobo forums for this issue, not this FSUIPC forum. Sorry, but I can only help with FSUIPC issues, not MSFS issues. I will leave this post in case anyone else has any suggestions, but you are better off using the Asobo forums for such issues. I have also moved your post to the FSUIPC7 / MSFS forum as you posted in the main support forum. John

In what way? They should have been the same... InBuilds did say: so they have no issues with the FSUIPC WASM. Yes - in the WASM persistent storage area, under your AppData\Roaming folder. See the Advanced User guide (WASM section) if you don't know where this is - the details are there. Please only attach this file after exiting MSFS. Your FSUIPC7 log files look ok. Do you have anything else om your Community folder? If so, have you tested with these removed? Does this occur in MSFS2024 only, or also in MSFS2020?

Yep - all looks good now! Cheers, John

I don't have the A300, and, as I said, I cannot see how the FSUIPC WASM module can freeze the sim, especially just for this one aircraft. But I need to see the log files as mentioned in my last post before anything else. What were you using before? Are you using FSUIPC7? You only need the FSUIPC WASM module installed for the following reasons: - using presets/hvars/lvars/calc. code functionality in FSUIPC7 - if using any other add-on that requires it John

Looks like your Saitek Pro Flight Rudder Pedals weren't connected - are you still using these? Please try the attached ini - this shou;d correct things (your registry now looks good!). Connect the rudder pedals, if using, start FSUIPC7 and exit and show me the files again. John FSUIPC7.ini

I don't know what that is, but looks to ne an error with ProSim reading the NavData database - you should ask ProSim. Yes - but no log file attached.... it looks like you are using offsets in the range assigned to "Nico Kaan for Lekseecon(Level D 767, 757)" for this. The landing gear is not assigned in FSUIPC, so I can't really help. Presumably you get the same if you try and move the landing gear lever in the VC? This sounds like an issue with the aircraft (ProSim), or possibly wherever your Landing Gear is assigned. I think you should ask ProSim about this. You should also update FSUIPC6 to the latest and only supported version, 6.2.1 (you are using 6.0.5). John

These are the registry entries, with the ones causing issues in bold: To correct this, first takw a back-up of your refistry (using the Windows Registry Editor). Then unplug the following devices (without FSUIPC or the FS running!): WINWING URSA MINOR CIVIL FLIGHT STICK R WINWING MFD1-L WINWING MFD1-R WINWING Orion Throttle Base II + F18 HANDLE Then download and run (i.e. double-click it) this file: removeDevices.reg Reboot your PC, then re-connect those devices. Then run FSUIPC7 and exit, and show me those 3 files again. Everything should be ok, but I will check the files just in case there is an id or GUID change that may need correcting. John

The latest official version, 7.5.0, is available from the two official places, the Download Links -> Updated Modules section of this forum, and at fsuipc,com. Better to always use fsuipc.com as these forums will soon be removed... The very latest beta, 7.5.1b. is only available as an exe and is posted in the forums. This version just has a few minor things added to assist with people using FSUIPC add-ons/3rd-party software that has not yet been updated for MSFS2024 - you only need that version if you have some issues with other software that uses FSUIPC. You need to install 7.5.0 using the installer first, then if you want to try this version it is available in this topic: John

Yes - although that surprises me as I didn't think the conversion was applied there...I think you can also log as SA32 (signed angle in 32 bits) to get degrees, rather than S32. But using lua is easier than extracting from the log.

First you need to get the correct values. Offset 0x057C is 4 bytes (S32) and not 1 byte (S8), and for degrees you need to *360/(65536*65536) this value - please see the Offset Status document for details. The easiest way to get this into a format to graph/chart is to write the value (preferably already converted to degrees) with a timestamp to a csv file using lua. There is already am example script provided that does this, called record to csv.lua and can be found in the Example LUA plugins zip file, in your FSUIPC Documents folder (see the Lua Plug-ins document for details on the examples provided). You should easily be able to adopt this script for your needs, removing the current data written/offsets read, and just read offset 0x057C, convert the value to degrees and then write that together with a timestamp.

Ok - thanks for the update. Glad its all now working. Regards, John

So its not anti-virus software on your PC that is detecting this? Uploading there says that 1/56 security vendors flag it as suspicious, but not which vendor it is. The false-positive needs to be reported to the vendor. As I said, there is nothing wrong with the downloadable installer - it is a false-positive and I can do nothing about this, it needs to be fixed by the vendor. John

You should use FSUIPC's logging facilities to work out what is happening. Set logging for Buttons & keys, open the logging console and see what is logged when you press the buttons - this should tell you what is happening. But if button 0 is already pressed when you press button 1, line 34 will NOT be triggered as that assignment is on button 0. Assignments are only triggered when the main/assigned button is pressed/released, not when the compound condition is changed. So, assignment 34 should be on button 1 with the compound condition on button 0 being pressed, i.e. 34=CR(+0,0)0,1,K190,8 -{Key press: .>key}-

Was this working in 7.4.18? And if so, how? If its using FSUIPC's virtual buttons, there must be something (a lua script perhaps?) that sets this up. There is nothing native to FSUIPC that would recognise this device and do this automatically.

Then it is probably the same issue, no? i.e. an invalid OneDrive registry entry - maybe @SaganLo can advise on how he solved this, although it was over three years ago.. That is NOT the recommended location - that location should be used for the add-on.xml file only. It is recommended to install in a non-windows folder, e.g. C:\FSUIPC6, or C:\P3D-AddOns/FSUIPC6.

It seems that you are having such issues as your registry is in a mess: If you can show me all 3 files (.log, .ini and .JoyScan.csv) we can correct this which should prevent such issues re-occurring.

Sorry but you are now confusing me. Are you now saying that it is not detecting button presses? What has this got to do with keys? Or what key press are you expecting to be recognised in the button assignments panel? Can you please be clear - buttons and keys are different.... If issue an issue with button presses, is this for one specific device or for multiple/all devices? Your log file does show some registry issues, but 8 devices are detected/acquired... I think you need to explain your issue more clearly if you want assistance... Is that this device: ? Can you see the axes dor this device in the axes assignment window? Then you need to use a (free) file transfer service... Also, please attach your FSUIPC7.JoyScan.csv file. I am finishing now for the day - I will check your files tomorrow now. John

Maybe, but as I don't know what you are doing, it would be helpful if you could answer my questions. Again, once you have pressed the Set button, does the text in the key-entry box changes to PRESS KEY? And then no key presses are recognised? And if you click on the PRESS KEY text box (to give it the focus) and try again, is it recognised then? You can compress/zip it if its too large. Your upload limit will be very low as you are new to the forum, it will increase the more you post. I just want to check if you have any options set that may affect this, such as using a keyboard hook. John

Presumably you have pressed the Set button, and the text in the key-entry box changes to PRESS KEY, no? And then when you press a key this is not detected - is that correct? Can you show me/attach your FSUIPC7.log and FSUIPC7.ini files please.

But the message before this was that you were getting a CTD with FSUIPC7, The log file you attached was NOT from a CTD. And if the error was that the controllers weren't recognised, I don't see a key-press assignment triggering a recan. Did you do that? You log shows some keys being pressed, but nothing that triggers a rescan, and the sim was shutdown after 83 seconds: And it looks like your device was not detected by FSUIPC7 when it was initially started: There are also various messages like this: so it looks like the device is continually connecting for some reason. Check for any driver updates for this device. It is not a standard windows HID-joystick type device, and it looks like the connection between the device and the wifi dongle isn't very stable... Can you please give details and what happened and what you did the next time you attach any files. May be worth doing this with the logging console window open as well (Log -> Open Console...) so that you can see the messages logged in real-time.

What was quick? The log file you attached shows no errors and that FSUIPC exited normally as MSFS had exited. Please provide more information when you post - what did you do and what happened? Also check your GameSir-Dongle is in a correct port - if its USB2, male sure its in a USB2 port and if its USB-3 make sure its in a USB3 port.

I don't understand why you are reporting issues and not showing me any files so that I can take a look. Please at least attach your FSUIPC7.log file if you are getting any issues. If a device stops working, can you please open FSUIPC and go to the axis assignment tab and see if the devices' axes are recognised there, and also check the button assignments tab to see if your buttons are recognised. Also try restarting FSUIPC7 - is it then recognised? Can you also check the USB hub settings (in windows device manager) and make sure 'Allow the computer to turn off this device to save power' is unchecked/disabled for all your USB hubs and devices.

Where is the landing gear assigned? Are you using FSUIPC for this? If so, please show me/attach your FSUIPC6.ini and FSUIPC6.log files, the latter with logging for Events and Buttons & Keys activated. John

You also have an unrecognised device: You have re-assigned to this as device C. You should remove all assignments to device A and remove that line, i.e. these: John