John Dowson

To use PMDG custom controls via FSUIPC, please see those 2 FAQ entries. All the information you need is there - I am not going to explain that again here... Why are you doing this? Just open up the button assignments panel, turn your rotary or press a button, and the button should be registered and you assign the custom control. You don't need logging. This is correct. The parameter is either the mouse operation, or a value. Using a mouse operation as a parameter should produce the same effect as clicking the mouse on the rotary in the VC, i.e. a single inc/dec in each direction. When programming a rotary that controls different things based on a selector, you would need to overload the in/dec rotary (i.e. multiple assignments for each quantity you want to change) and use either a compound button assignment so that only the control is send based upon the position of the mode selector switch, or an offset condition based upon the position of the mode selector switch in the VC. To get better control, and implement both fast and slow inc/dec, you would need to use a lua script. The script would, on each rotary button press, need to read the current value for what is to be inc/decremented, apply the relevant delta value (i.e. increase or decrease this read value by an appropriate amount) and then use the custom controls to set the new value. I don't have any PMDG aircraft for P3D, but I can take a look in the MSFS version if you need further assistance, and if it works in the MSFS version it should work in the PMDG version once any control/offset numbers have been checked. I won't have time to look into this until later next week though. John

Trim wheels usually work on buttons, not an axis. Some have two buttons in each direction (one for fast movements and one for slow), others just one. For those using just one button, you can use the Rotaries.lua script to convert this to use two virtual buttons instead, to enable fast/slow trim in each direction. The Bravo trim wheel has one button in each direction. I showed how to configure the Bravo for basic operation, including the trim wheel, in the following post: That should work for quite a few aircraft, but it won't work for all aircraft, especially many add-ons, as those assignments use the default FS controls. For such aircraft, you should use a profile and override these with the specific controls for that aircraft, whatever they may be - usually using presets, input events or lvars. There are also many other ways yo assign trim, and it is up to you to decide what works best for the aircraft you are using. For example, see the following post: John

I will update/replace the trial license in a few days. For now, I have PM'ed you both the latest trial key file, valid until 1st Feb. John

@biggstuff and @Krčík Robert: I have checked both your keys, and as expected they are both fine and validate without issue. As I keep saying, read the Installation and Registration guide and follow the instructions there.

For a new PC, make sure you have downloaded and installed the latest VC++ redistributables, otherwise the registration details won't validate. Please see the Installation and Registration guide for details. And have you read the Installation and Registration guide and followed the instructions there? I am not going to check your key until you have done this. I have checked hundreds (if not thousands) of keys over the years and all have validated successfully, i.e. ALL registration issues are either due to user error or having the wrong VC++ redistributables installed or anti-virus software (see documentation for full list of known possible issues).

@Eduardo P You have cross-posted - please don't do this! I have enough to do all ready without having to answer the same question from the same person multiple times, especially when the question has been asked many times before and the answers are in the documentation.... See

If you registered once, why are you registering again? You don't need to do this - once you have registered and have an FSUIPC7.key file you can just skip registration. And if it registered once, your leu is fine an there is no point me checking it. Please see the documentation for ALL issues with registration. John

Are you aware that the (optional) desktop icon(s) that are installed by the installer only start MSFS2020 and MSFS2024 - they do NOT start FSUIPC7 by default, They are only used to start FSUIPC7 if the MSFS.bat auto-start method is selected during installation. By default, it is MSFS that starts FSUIPC7 via the EXE.xml file. To start FSUIPC7 on its own, you need to double-click the FSUIPC7.exe.... I don't understand why I keep having to explain this time and time again when this is all well documented and also in hundreds if support requests. PLEASE read the documentation! What do you mean by this? If you mean the FSUIPC7 is not running, then run it. If you have in stalled an auto-start component and it isn't auto-starting, see that FAQ entry. Then you are either looking in the wrong place or FSUIPC7 is not running. Try reading the documentation, check your InstallFSUIPC7.log file to make sure everything was installed correctly, and see that FAQ entry if its not auto-starting.

I cannot help with MSFS, only FSUIPC...does FSUIPC recognise your devices? FSUIPC will only recognise buttons/axes on HID joystick type devices. If it is a non-joystick type HID device, then the buttons/axes will not be recognised in the FSUIPC assignment panels, but you can possibly use lua to control this device. You could try uninstalling the Elite drivers and see if windows installs default drivers and if your device is recognised with those. However, if using the Elite drivers, I think you will need Elite support for this issue. Someone posted a similar issue but with FSX in 2008 but it looks like this was not resolved, see: John

As I said, by default FSUIPC7 starts iconized to the system tray, except if a new version is available in which case it will start with the main window open. There is an ini parameter you can use to control this behavior: Happy New Year! John

And a Happy New year to you as well! John

When FSUIPC7 starts, it shows a splash screen then is iconised to the system tray. You open it from there, or can use the (default) hot-key assignment of Alt+F to open the FSUIPC7 main window. i presume you see the splash screen, as you say FSUIPC7 starts, but do you see it in your system tray? if so, and opening it (either via the task bar icon or using Alt+F) should move it to the task bar and show the main window. If you can't see the main window, it is being positioned outside of your screen area. To fix this, exit FSUIPC7 and remove the Window ini parameter from the [General] section of your FSUIPC7.ini file. If you can't see it in the task bar, please check if it is actually running or not and show me your FSUIPC7.log file.

👍

See the following FAQ entry for this issue: Check your InstallFSUIPC7.log file for any issues/errors, and check the contents of the EXE.xml file to make sure it is valid. Usually such issues are caused by another add-on writing a corrupt EXE.xml file. If that is the case, just delete that file and re-install. You can post / attach both files here and I can take a look.

Thanks for the update. Previously windows would ask for a new username/password if the account couldn't be elevated correctly so this behavior must be relatively new... I will add a section in the Installation guide about this issue. Anyway, glad its now working! Regards, John

And how did you solve it then? It is not a WASM or FSUIPC issue. Check the Asobo forums for similar reports. That is very strange... I was going to suggest monitoring the pause state in case that has been triggered, but if that was the case you wouldn't see this. Can you set logging for Events in FSUIPC, and when this happens again show me the FSUIPC7.log file (after exiting). So esc doesn't work? What about the FSUIPC option MSFS->Exit?

What actually happens when you proceed? Is an InstallFSUIPC7.log file created, and if so can you please attach it. Do you have a UserCfg.opt file under: %APPDATA%\Microsoft Flight Simulator\UserCfg.opt? If not, where is this file located? In that file, what is the setting of the InstalledPackagesPath variable at the end of the file? Is your APPDATA environment variable set correctly?

Ok, so MSFS froze? If so, how did you close it? Does FSUIPC still work? Via the FSUIPC_WASM.ini file - see the documentation (WASM section in Advanced User guide). It sounds like your issue is with MSFS, not the FSUIPC WASM. If MSFS has frozen, so will the FSUIPC WASM module. If the WASM module crashes, MSFS should go on regardless,,, Note also that there were very few changes from 7.5.0 to 7.5.1, and no changes at all in the WASM. I suspect your issue may have been caused by a sim update that happened at about the same time.

What does this mean? Deleted what changes? This makes no sense... Why do you think the WASM had crashed? Was MSFS still running when you attached that file? If so, please always exit MSFS before attaching a WASM log file. If the WASM did crash, it certainly didn't crash when scanning for lvars and I will need more information . Please set Debug level logging in the WASM and show me a log file with that enabled, and attached after exiting MSFS. Also please set Debug level logging in the WAPI (FSUIPC menu bar, Log -> WAPI -> Debug) and attach your FSUIPC7.log file as well as your FSUIPC_WASM.log file.

It really helps if you can be more specific about what actually happens. What should happen straight away after starting the installer is that a windows box should appear asking if the application (from an unknown publisher) can make changes to your system. You should then click Yes, which then gives the installer elevated privileges and starts the installer. Then, it shows the welcome page, you cluck Next and if you have both MSFS2020 and MSFS2024 installed, it should show a screen that allows you to select the version, otherwise it goes to the license agreement page. What do you see? What versions of MSFS do you have installed, and are they via Steam or MS Store?

You say your WASM is crashing. I therefore need to see a log file for this, preferably with Debug level logging enabled. There is no point attaching a log file from a session where it didn't crash.

The log file shows that FSUIPC7 exited as MSFS had quit: Are you saying that MSFS was still running? If so, try setting DisableMSFSMonitor=Enum in the [General] section of your FSUIPC7.ini file. This is needed (and added automatically) in Windows 11, but shouldn't really be needed in Windows 10. However, if FSUIPC can no longer see MSFS and thinks it has exited, then you should try with this set. Otherwise, you could disable the auto-exit feature (uncheck Options -> Exit with FS).

What do you mean by this? How do you know it has stopped? How do you restart it? Do you have to kill it first? The log file you attached ends after 5 seconds, and shows FSUIPC still running after being started at 14:25...did you attach the wrong file? If you restarted FSUIPC, it would be the FSUIPC7_prev.log i would need to see.... If it is presets that stop working, you could be suffering from a WASM crash, but then restarting FSUIPC would have no effect. I really need more information and a log file from when this occurs.

That looks ok but could be cleaner, and some of the numbers are incorrect... You don't need to test check_lights for 0 - just set it to 0 and use variables local to the function, e,g, Logo lights are bit 8, so 2^8=256, so should be: Also wing lights are 2^7 = 128, etc...

All such connection issues, especially after a windows update, are usually due to either Workgroup name changes of firewalls being reset. So please double check these - the Workgroup name on both PCs, and try disabling ALL firewalls - client, server and router, to see if that makes a difference. Also, please attach your WideClient.ini for such issues, and always exit P3D/FSUIPC before attaching files. Have you tried setting the ServerName (or ServerIPAddr) and Protocol WideClient ini parameters? If not, please try that. Please review the section Configure your Network in the WideFS User guide, If running as Admin, you may need to run WideClient as Admin as well...