John Dowson

I need to see this file. It should not be that big, but try zipping/compressing and then attach - it is a text file and should compress to a small size. John

Are you using Windows 11? If so, please see the provided README.txt: John

Also, just check your FSUIPC7.log file. Maybe the lvar wasn't available to add to an offset once you loaded the aircraft? This can happen with complex aircraft as it can take up to a minute or longer before all lvars become available. You can adjust when FSUIPC scans for lvars by setting the LvarScanDelay WASM ini parameter to a higher value. Its default value is 5 (seconds). I use a value of 45seconds, but some folks find that a minute or longer is needed. This depends on your system and the aircraft in question. Please see the Advanced User guide on how/where to use/set this parameter. John

It comes with the installer. Just download the latest version and run the installer. Not if you want to continue using the MobiFlight events via FSUIPC event files. You can do things without the MF WASM, but you would have to stop using the MF events and re-program those assignments to use lvars, hvars or calculator code. This is quite straightforward for most MF events, as they just set lvars or activate hvars, but some are more complex and require compound assignments. For the time being, it may be easier to continue using the MF WASM module. For the next FSUIPC7 release, I am planning to implement a mechanism that sends calculator code directly from predefined custom events, such as those listed in the MF events.txt file, and to also allow parameterized custom user-defined events. This should remove the need to use the MF WASM module entirely. I will publish details hwen ready. John

You can use either. If using set, make sure you are setting to 0 for off and 1 for on. If using toggle, you can add an offset condition so it only toffles depending on the current value. If you do not understand what that means, use set. Please: 1. Activate debug level logging in the WAPI. To do this, add the following to the [WAPI] section of your FSUIPC7.ini file: LogLevel=Debug 2. Set Log->Buttons & Keys in the FSUIPC7 menu. 3. Load your aircraft and press the assigned button 4. Exit FSUIPC7 5. Show me your FSUIPC7.ini and FSUIPC7.log files. John

No...why do you think that? For PMDG aircraft, you have to use their SDK - custom controls and PMDG offsets. See the included document on PMDG offsets Offset Mapping for PMDG 777X.pdf, and check out this FAQ post on how to use PMDG custom controls: It will be in your FSUIPC5 Documents folder, which should be under your Modules folder. The upgrade price from FSUIPC5 to FSUIPC6 is 9.99euros (+ tax). You should get that price automatically on checkout if you have purchased a license for FSUIPC6. But maybe you don't need this, up to you... John

Two things may apply: 1. When you manually change the ini, you need to either restart FSUIPC for these to take affect, or, usually if it is an assignment you are changing, you can reload the assignments from the UI assignment panels (see the reload assignments button in each panel). 2. Sometimes lvars are not available on the initial scan for lvars. You can force a rescan/reload of lvars using the Add-ons->WASM->Reload menu option. For complicated aircraft, it can take up to a minute after the aircraft has loaded for some lvars to be available. There is a parameter that you can set in the WASM ini file (FSUIPC_WASM.ini) called LvarScanDelay. This is, by default, set to 5 seconds. I use a value of 45seconds, but some folks have this even higher. The correct value depends upon your system and the aircraft you are using. If you find that the lvars are not initially available, try a reload to see if they then become available, and if they do, try increasing this scan delay parameter. John

Of course! The ini file is where FSUIPC saves the assignments you make in the UI. Why are you using set rather than toggle (as the example I keep referring you to in the advanced user manual)? With that assignment, you are setting the lvar to 0, i.e OFF. But does the master caution turn off in the aircraft? That is what this assignment does. What happens to the bravo lights is another matter, and that depends on how you are controlling the bravo lights (are you using AFC Bridge? Or the FSUIPC lua scripts?)- this is a separate issue. On the Bravo or in the aircraft? If this works when you change the lvar value using the Add Ons -> WASM -> Set Lvar... menu, it will work via an assignment. If its not working, try logging - add debug level logging to the WAPI (by adding a LogLevel parameter to the [WAPI] section of your FSUIPC7.ini - RTFM) and button & key logging in FSUIPC7 via the log menu. Then keep the logging console open so you can see what is happening when you press your assigned button. John

You are confusing two different methods. One method is to add the lvar to an offset, AND then use an offset manipulation control on that offset - you DO NOT need a macro file. The second method is to use a macro file. If you are using a macro file, you DO NOT need to add the lvar to an offset, So, in this case, as you are adding the lvar to an offset, just remove the macro file. Then, assign your button (or key press) to the Offset Byte Togglebits control, giving the offset value as 0xA000 (the offset you are populating), and the parameter as x1. This is EXACTLY the same as the example given on P45 of the Advanced User guide, except that you are using a different lvar name - but it is still a boolean type variable (with values 0 or 1). What is so difficult to understand about this? Can you please explain as I am getting pretty fed-up of repeating basic information when I have spend a lot of time to provide user manuals for this.... Also, please remember that you should NEVER manually change the [MacroFiles] section in your ini (as with many other sections). This is managed by FSUIPC and should never be manually changed, unless you really know what you are doing. In fact, never change anything in your ini unless advised in the documentation or by support. There is no place that says you should manually adjust this section. Any issues, try looking at your FSUIPC7.log file. This should indicate any errors, and you can also add more logging via the FSUIPC7 Log drop-down menu. You should learn how to use these facilities and understand what is logged, to help you solve your own issues, although I am always here to help - but that should be a last resort... I have now had many many support requests like this, and, to be honest, it is becoming a bit of a pain, as it is always the case that the manual hasn't been read or followed, and i am endlessly repeating myself. This takes time away from more useful activities, such as improving the documentation (which nobody seems to consult anyway...) and adding new functionality.... John

I am also looking into making calculator code easier to use in the next version of FSUIPC7. I will publish exact details when this is released, but the general idea is to allow you to define paramterised calculator code and give that a control name, which you can then assign to directly in the control menu drop-downs. I will use the same format as the MobiFlight events.txt file (except parameterized, i.e. allow a parameter in the calc. code that is replaced by the value you define when you assign to that control) so that the MobiFlight events.txt file can be used directly, i.e. without having to install the MF WASM module or any FSUIPC event files. John

Please see the following post: That is for FSUIPC6 and using PMDG aircraft, but the technique is the same. The controls you assign to will be different however, and that depends upon which aircraft you are using. You can try the default controls - and always a good idea to set this up using default controls in your default profile, and use profile-specific controls for aircraft which use different controls. It is up to you to determine which controls to use for the aircraft that you have loaded. John

No. Can you please show me you FSUIPC7.log file from when it crashed. Also please attach your FSUIPC7.ini file. Does this mean that if you just restart FSUIPC7 it will not connect? If that is also an issue, can you also show me the FSUIPC7.log file when this occurs. Thanks, John

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