John Dowson

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

The last log file you attached when FSUIPC was still running - please exit FSUIPC before attaching any files. Ok. The next time this happens, can you open FSUIPC and go to the axis assignment panel and see if your axis is recognized. 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. Also check if its a USB-2 device it is connected to a USB-2 port, and if its a USB-3 device its connected to a USB-3 port.

Could you please set a custom log value (Log->Custom) of x200000, also set logging for Buttons & Keys, and show me your log file and JoyScan.csv file the next time you get this issue. Also, please check your key assignment for this, and make sure you have checked No repeats!. It could be repeating which is causing issues updating the files... John

I cannot help with MobiFlight or Linda. FSUIPC will only recognize HID joystick type devices in the assignments panels. Your devices are HID but not "joysticks". The only way to assign to such devices in FSUIPC is by using the lua com library. This is what LINDA is using - LINDA is an interface to FSUIPC's lua scripting interface. A similar issue was reported several years ago, although using P3D - see Maybe try contacting that user to see if he has aby advice. Sorry, but I can't really help you any further with this hardware.

I really can't see anything in that video... can you please attach your files, your FSUIPC7.ini and FSUIPC7.log files. For the latter, please activate logging for Axes Controls, load your aircraft and move the throttle through its full range and back again, then exit before attaching the files. Normally such issues are because the throttle is assigned either to multiple axes or in multiple places. In MSFS2024, check that you have no assignments to the throttle in both the general settings and any aircraft specific profiles.

Can you please also show me / attach your FSUIPC7.ini file. Your log shows some issues with a lua script: Could you also attach that script please. If you exit FSUIPC and restart, does it then work or not? if not, can you exit MSFS and also attach your FSUIPC_WASM.log file. Then I need to see the log file from that session - the one you attached shows that FSUIPC exited normally, so I presume that was from a different session, no? So if one device stops working, does the other still work? Is it just assignments to presets/lvars that stop working, or all assignments? If you exit and restart FSUIPC, does it then work or do you have the same issue? Please supply further info, add/attach your log and ini files and check to see if the WASM has crashed or not (exit MSFS and check to see if the WASM exited cleanly or not in the WASM log file). John

Your log files also show an issue with one of your lua scripts that needs investigating: John

But the 7418 log shows that FSUIPC7 hadn't even connected to MSFS before it exited.... So it is working ok in 7.5.0? Was this with the Init3308 ini parameter added? I don't think so as you are using 7.5.0 - please try with the 7.5.1a version and use that - this ini parameter won't do anythung in 7.5.0, so you need to use the later version... This log file shows that when it is failing, the software is reading 0E (14) from 0x3308: The value 14 signifies MSFS20245. From the 750k version it is reading 0 (i.e. not yet populated): So it looks like it is the new value of 14 in offset 0x3308 that is causing this 'subscript out of range' issue. Really, the software needs updating to recognize this new number for MSFS2024. Failing that, you will have to manually set/change this number to 13 when set to 14. This offset is set as soon as FSUIPC establishes a connection to MSFS. So what you need to do is to change this value to 13 once 14 is written to that offset. It is not possible to update offset 0x3308 in the current version, so please try the attached version below, 7.5.1b, where it is possible to update this offset. To do this, create a lua script called ipcInit.lua and add the following: ipc.writeUW(0x3308, 13) If you do this, 14 will be written to offset 0x3308 when FSUIPC connects to MSFS2024, then the lua script will run automatically and change this value to 13. If the GSTEP software is started after the value has changed to 13, you should be ok. John FSUIPC7.exe

What antivirus software are you using? This will ne a false-positive, You need to either disable the anti-virus while downloading/installing, or add an exception to allow it to be downloaded and ran. You should also report this to the antivirus provider and they will check it and update their definitions. Note that this has already been reported for Kapersky:

From the comments this seems to be an issue with the FSUIPC WASM module and not FSUIPC itself, no? If you remove the WASM and just use FSUIPC, does it work? I don't know how FSUIPC could cause a plane to freeze, especially as the aircraft is not using FSUIPC or the WASM module. Is the WASM module crashing or exiting correctly with MSFS? Could you show me / attach your FSUIPC7.log and FSUIPC_WASM.log files from when this happens and after you exit MSFS / FSUIPC7. Also please activate WAPI debug level logging in FSUIPC7 (Log->WAPI->Debug) and also in the WASM module (via the FSUIPC_WASM.ini file). As you are a new forum user, you will have a very low limit for attaching files, so you may need to compress/zip them.