John Dowson

But I thought the FSUIPC main window was being displayed but it was blacked-out? If the FSUIPC window isn't being displayed (and just the P3D window is blacked-out), then it could be being displayed off-screen. To correct this, remove the following line from your FSUIPC6.ini file (in the [General] section): OptionsDialogOffset It is this parameter that controls the positioning of the FSUIPC main window. Removing that and it should default to displaying in the centre of the P3D main window. No. That is where the add-on.xml file is created to auto-start FSUIPC with P3D. It is better to have your FSUIPC installation in a separate folder. That did used to be the default installation folder as well, but this has now changed to C:\FSUIPC7, but if you are re-installing it will always provide the default location as your previous installation folder. Best to change this to a non-windows protected folder. Don't forget to move your files (FSUIPC6.ini, FSUIPC6.key, *.lua, *.mctp, *.dll) across to the new installation folder if you change your installation location. John

Sounds like you are doing everything correctly.... Could you please do the following: - activate debug logging in the WAPI. To do this, add the following line to your FSUIPC7.ini file under the [WAPI] section: LogLevel=Debug - activate logging for Buttons and Keys in FSUIPC7 (Log -> Buttons & Keys) - produce a short log file where you load your aircraft and then press the button you have assigned - exit FSUIPC7, and then show me/attach your FSUIPC7.log file and your FSUIPC7.ini file Thanks, John

That calculator code just activates the hvar. To use hvars in FSUIPC7, you first have to make them known to FSUIPC7 using hvar files. Hvar files for the FBW A320 are provided in the HvarFiles sub-folder of your FSUIPC7 installation., To use these, you need to move or copy them to a location where they are recognised by FSUIPC7, and also rename them to give a substring match on the aircraft that you are using. Details of this can be found in the Advanced User guide, page P45). Once the hvars are known to FSUIPC7, you can try activating them using the Add-ons->WASM->Activate hvars... menu option. To assign to activate a hvar, you need to use a macro file. See P37 of the Advanced User guide on how to to this. Once the hvar is known to FSUIPC7 and made available in a macro file, you can assign to activate that hvar on a button or key press in the usual manner, by selecting the macro/hvar name from the controls drop-down. John

The easiest way to do this is to add the lvar to an FSUIPC offset, and then assign to one of the offset toggle (or set) controls, To do this, please see the section Adding Lvars to Offsets on P44 of the advanced user guide. You can follow the example given - just update the lvar name to the one you want to use (and your profile name). Any issues, try searching this forum before posting again (I have explained how to do this many times now...). John

Not sure what this means... renaming the key file will run FSUIPC7 as an unregistered version, so you will not see an assignments menu. Alt + F does not invoke any menu, but should display / hide the main menu. I am not 100% sure from your response, but it seems like FSUIPC7 is working ok when unregistered, no? Hmm, maybe this is causing issues. It looks like, when FSUIPC is running as a registered version, it is crashing when trying to access your registry. I would like you to try running FSUIPC7 without MSFS, i.e. do not use the MSFS2020.exe, the desktop icon or the MSFS.bat - just start FSUIPC7 directly from the FSUIPC7.exe please. Could you try running that as explicitly as admin, i.e. select the FSUIPC7.exe, right-click and select Run as administrator. If it still crashes, can you: - rename your FSUIPC7.key file again and run FSUIPC7 as unregistered - Go to Log ->Custom and enter the value x200000 - exit FSUIPC7 - restore your FSUIPC7.key file - run the FSUIPC7.exe again as administrator Please do not run MSFS when doing this. The issue with FSUIPC7 has nothing to do with MSFS and it is better to try and get to the bottom of the FSUIPC7 issue without MSFS for the time being. John

But you have already said that the standard controls don't work for that aircraft, so there is no point logging your button presses - which your log just confirms are working and sending the assigned controls. You need to find out what, if any, controls work for the aircraft. For this, you activate the trim in the aircraft UI, and see what, if any, events are logged. If there are any, try assigning to those. Otherwise, see if the aircraft comes with its own SDK and/or custom controls. Otherwise, try asking the developers of the aircraft - surely they have a support forum? John

I am not sure what you expect me to do with that... I suggest that you keep the logging console window open. Then, activate whatever function that you want to program in the UI (i.e. the trim) , and take a note of what event, if any, is logged. Then, try assigning to that event. I cannot tell from your log file when you are activating the trim in the aircraft UI - only you can do that... John

Always better to attach files. That looks ok, except the first line is missing - here's mine: So you now cannot see the FSUIPC7 main window at all? What happens when you double click the FSUIPC7.exe (without starting MSFS)? Do you see the splash screen? Does it then crash or sit iconized in your system tray? If the latter, can you see any events in the windows event log? It does look like FSUIPC7 is crashing during the device scan. If FSUIPC7 is crashing on start-up (which it looks like) could you try renaming your FSUIPC7.key file, temporarily, to FSUIPC7.key.unused, to see if it then runs and displays (although you will not have access to any assignments when doing this). This will bypass the device scan. You also seemed to have installed FSUIPC7 under an 'Admin' account. Why is this? Are you running FSUIPC7 with admin privileges? If not, you could try that. If so, try without. Also please show me your InstallFSUIPC7.log and FSUIPC7.JoyScan.csv files. I don't think they will show anything, but I would like to check. Your issue is very strange.... John

I will take a look at that when I get time - may take me a few days though. You should really try these things before purchasing... Really don't know what to say. As I said, I had it up and working within a few minutes without issue. Have you configured to use with FSUIPC or without? Did you try both assigning to FSIUPC offsets and MSFS events, as I showed you in the pictures in my previous posts? FSUIPC will not recognise the buttons on these devices - this is why you need to use SPAD or SPAD.next. As it seems you have purchased SPAD.next now, you should use there support services to resolve your issues when using this. I will take another look at the original SPAD, following that post, to see if I can get it working with MSFS. John

Good to hear! All your FSUIPC documents will be under your Windows Documents folder, in a subfolder called FSUIPC6. There should also be a link to this folder from your FSUIPC6 installation folder, but looks like that isn't created any more. Not sure why - I will take a look and fix that. I am sure the manuals can help you, so do try to find them. They are also available as a separate download, but these will not be as up-to-date as the ones installed by the installer. See . John

Try activating logging options (for events initially, and also maybe axis controls) and trim in the UI to see what events that aircraft is using. Or maybe check for custom events or lvars. If you can figure out what is controlling the trim, it should be possible to set it up (via a custom profile) specifically for that aircraft. Unfortunately I don't have that one, so can't really assist with this - just give you general guidance on what to try. John

That is interesting - could you share this? And does it work with MSFS? If you share the workaround, I can take a look with SPAD. If it is working, try setting to the FSUIPC offsets that I indicated in an above post. If its working with MSFS, that should do it. That i strange, I did use SPAD, many years ago, but switched to SPAD.next as I found it a lot more advanced and user friendly. There are many profiles for existing aircraft that you can import, and modify as needed. I think you are only allowed one trial period per email address, so you may not get the 14-day free trial again. They (Ulrich) is very responsive though, so if you don't get the 14-day free trial, you should email their support and request another free trial period - I'm sure they will oblige John

It should work with most aircraft, but maybe not with complex add-ins such as the FBW A320. May even work there though, but I haven't checked. Just needed to add a disclaimer as I haven't, and can't possibly, try each offset with each aircraft, default (i.e. included) or otherwise. John

Generally yes, although this can depend on the aircraft in question. Some aircraft (especially add-ons) may not use the standard control/event that this offset uses. John

Now done, will be included in the next release. John

Are you still experiencing this issue? If so, you should try updating your VC++ redistributables, as these are known to cause many strange issues. Install the latest combined redistributable package from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist (both x84 and x86 versions are recommended). This will install the redistributables for 2015, 2017, 2019 & 2022. If you have any of these installed individual, uninstall first before installing the combined package. John

Any success with this?

Thanks for the feedback. These changes will be incorporated into the next official FSUIPC7 release. Regards, John

If you do have SPAD working with MSFS / FSUIPC7, then the gear lever offset is 0BE8, with value 0 for Gear Up and 16383 for gear down. John

Ah, but from your image I see that you are using SPAD and not SPAD.next... I don't think the orifgnal SPAD works with MSFS - I did try this but couldn't get it to run. The development on SPAD stopped in 2012, over 10 years ago. I suggest you try SPAD.next if using Saitek devices such as the multi-switch panel or radio panels. These will not be recognised by FSUIPC. You will have to pay for a license, but it does also come with presets for many aircraft, and I would consider it essential if using Saitek devices (other than the throttle and joysticks, X52, X56 etc, as these can be handled by FSUIPC). John

I have also switched the assignments to use the sim events directly rather than FSUIPC offsets, and this also works without issues: John

So, I installed SPAD.next. Configured it to use FSUIPC, loaded a default profile for the C172 then tried this in the JF Piper Arrow and the landing gear lever on the saitek multi-switch panel works as expected. Here's the SPAD.next configuration for this lever: John

What does this mean? Alt + F just displays and hides the FSIIOPC main window. You can see the FSUIPC7 main window can't you? The image you posted above shows it is displayed. What exactly is your issue? Is it that - FSUIPC7 doesn't auto-start with MSFS? If this is the case, show me this file: C:\Users\Admin\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml - there is no Assignments menu? Your log shows that your copy is FSUIPC7 is registered, even though your folder listing doesn't show am FSUIPC7.key file. However, it MUST be there as your lof states it has found these details: - FSUIPC7 exits/quits while MSFS is still running? If so, add this to the [General] section of your FSUIPC7.ini: DisableMSFSMonitor=Enum (see point 5. under Problems running FSUIPC7 in the provided README.txt). In fact, you should do this anyway as running under Windows 11. If you are experiencing strange issues, I also suggest that you install the latest combined VC++ redistributable package from Microsoft. Uninstall any individual packages first an then install the combined package - again, see the README.txt, item 1 under Problems running FSUIPC7. John

Great! Glad that issue is sorted. Cheers, John

I just disabled the abort when no P3Dv5 installation was found and set the flag that it was actually found (i.e. a hack!) If you re-installed windows, did you also install the latest combined VC++ redistributable package? If not, please do that - that may be the issue. John