John Dowson

You should never modify the [LuaFiles] section unless you know what you are doing. Deleting entries (added by FSUIPC) can also cause issues, as it is the index number of the file in this section that is used when you assign to a lua file. Better to never edit this section.

I would prefer if you posted any issues with the beta in the beta release post.... I hope you mean that FSUIPC detected the file and added it to the [LuaFiles] section, and you did not add this manually. If you added it manually, then remove it and try again and see if it is automatically added to that section. If it isn't, it is either in the wrong folder or has an incorrect extension. If it is in the [LuaFiles] section (and was added there by FSUIPC), it must appear in the assignments drop-down when Select for FS control is checked. If it isn't, please show me / attach your FSUIPC7.ini and FSUIPC7.log files. John

You would normally assign your POV buttons as an axis (i.e. under the Axis Assignments tab) to the Pan View control (with Send to FS as normal axis), so try that. Remember to delete the assignments to the POV buttons first. Note that when assigning this way, the up/down can zoom in/out, but also move the camera up and down (in the spot external camera and depending on the current camera position). This is the way the external camera controls work in external spot mode, at least in P3Dv4-6. I have no experience of using P3Dv3.

Yes. its strange that that happens... Thanks for the feedback! Cheers, John

Yes, I don't know what is setting that for some folks, but I presume its anti-virus software. Do you use any anti-virus software on top of Windows Defender?

Please use the specific sub-forum for all issues with FSUIPC7, not the main support forum. I have moved your post. There is nothing wrong with the installer, and you don't need to run it with Admin rights. Check that anti-virus software is not blocking it from running. Also check that you have the latest VC++ redistributables installed.. Do you see anything at all when you run the installer? If not, check the installer properties (right-click, select Properties). Sometimes it is blocked there from running. Note that you have to run MSFS at least once after installation before you can run the FSUIPC7 installer.

Your FSUIPC7 version is fine. You need to check your network. Please review the section Configure your Network in the WideFS User guide, and maybe add the ServerName and Protocol WideClient ini parameters. Also try with firewalls disabled (client, server and router) to see if a firewall is blocking the connection.

I need to see your FSUIPC7.log and FSUIPC7.ini files as well, and not your InstallFSUIPC7.log file. However, if this started after a windows update, you need to check your network set-up, especially the WorkGroup. Please see the provided WideFS documentation, and follow the set-up and trouble-shooting guides there. Also, if using FSUIPC7 version 7.4.18, check the build date (1st line of FSUIPC7.log file). If that says 1st November, please update - it should say 3rd November. You may need to clear your browser cache to download again.

Presume you mean 7.4.18, no? If not, please update. If using 7.4.18, please check the first line of your FSUIPC7.log file. If it has a build date of 1st November, i.e.: then please download and re-install. it should say 3rd November: The initial release was accidentally built using the SDK from MSFS2024, and I corrected this the following day, If that is not the issue, please show me / attach your FSUIPC7.log file. Ah...just seen your updates... Yes, that is definitely the issue - please update. John

You did not set this: That will always log the value it is using on start-up. You either set it in the wrong ini file, added/changed it while FSUIPC7 was still running, or maybe added it again and there is another entry.

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!