John Dowson

Yes, very strange... I will be releasing 7.5.1 later today, and I am going to switch to using version numbers on the downloadable file which should help with this cache issue. Cheers, John

Ok, sorry I cant be of more help. And a Merry Christmas and Happy New Year to you! Regards, John

...and I will be releasing 7.5.1 tomorrow (only minor updates to help users with 3rd-party software using FSUIPC that hasn't been updated for MSFS2024) so maybe try that once released.

I don't understand this, unless you download from here (i.e. these forums) and didn't clear your browser cache, in which case the older cached version was downloaded. The download forums on this server will be removed soon, so you should use fsuipc.com. I will be moving everything to there, and support via Discord, over the next few months... Regards, John

Ok, I have corrected it there. But you only need to download that if not using FSUIPC7. Yes, I updated this after the beta, or maybe in the final beta. It will overwrite, but I think this was changed a day after the initial release, so if you downloaded early it would have had the old value. As I said, I think the initial release still had this set as -15. As this was causing issues, especially in MSFS2024, I decided to make 0 the default, but I didn't release/update the version number for this change. If this fixes the issue, could you post this on the IniBuilds forums so that anyone who has this issue can check that setting. I still don't understand how a WASM crash can cause the a/c to freeze though, very strange.... John

What website? Use fsuipc.com, as the zip file may have been cached if using the download links in this forum. I have checked the zip file again and it is definitely set to 0.

Yes, that is an error and will be corrected in the next release, sorry. The log file shows that the WASM crashed. Try disabling lvar scanning, see the following FAQ entry: Basically you just need to set the WASM ini parameter LvarScanFrequency to 0. In fact. the latest release should have this already set, but may be overridden if you have an FSUIPC_WASM.ini file in your persistent storage area. If you do, remove that or change/update there. I don't see how a WASM crash can freeze the sim though, unless the A300 is using the WASM... John

But you don't have to go back to the main menu to exit the sim - use the FSUIPC7 menu option MSFS->Exit

Then the log file should be here: AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvarmodule\work i.e. under MSFS2020 not MSFS2024. There is an error in the document that I will correct. It will get created, as it is created when MSFS starts the WASM during start-up. However, if you kill the sim it won't exit correctly. No point in doing this.... Of the FSUIPC WASM module is installed, that folder will/must exist. You are just looking in the wrong place... The folder and log file will exist regardless of whether you use the WASM or not, if the WASM is installed.

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.