John Dowson

You can try as @Masteriussuggests (except edit as below), but that may not work either - sometimes you need to edit the registry to remove such entries. However, they are only warnings and not important - they won't have anything to do with your issue. Your Parking Brake isn't currently working as your 'A' device is missing. Changes the [JoyNames] section to the following:

First, you posted in the FAQ sub-forum, where it explicitly states (in several places) NOT for support requests. Please take care to post un the correct forum for future posts. We do not support x-Plane. Thats xpuipc by a different developer. FSUIPC7 is the version of FSUIPC that works with MSFS. and is a different product to FSUIPC5 and requires a separate license, available from SimMarket. A discount is automatically applied for FSUIPC5/6 license holders at checkout. FSUIPC supports all HID joystick type devices for assignments via its UI. For other HID devices, you can access via the lua com library

Why? Your ini and log tell me a lot more than a video can. I rarely watch videos for support requests - they are not needed except in exceptional circumstances (and don't have the time!). We prefer a decent description + log and ini files. You can do. Make sure to reload assignments if FSUIPC is running. Otherwise, you can clear it from the axis assignments panel.

Probably because its assigned to two axis - most likely one you are also using (assigned in P3D) to the rudder: Try deleting one of those - probably 2.

Keyboard input is received from MSFS via SimConnect as key input events, when MSFS has the focus. Commands are sent back (usually) as events also via simconnect. When FSUIPC has the focus, it receives the key events as windows messages. Yes, that would be the case when MSFS has the focus. See if there is a difference when MSFS has the focus vs when FSUIPC has the focus. John

Yes, your registration details for FSUIPC4 will be valid for all versions of FSUIPC4, and the same for WideFS7. The latest version of WideFS7 is 7.156.

Yes. If P3D/FSUIPC6 is running, you will not be able to run/start FSUIPC7, and vica versa, so if FSUIPC7 is running you cannot start/run P3D. Yes. Its not that complicated. You can have as many different FSUIPC installations as you like (same or different versions), but only one can ever be active at any given time. I wouldn't worry about it. Just download FSUIPC7, install it and try it out. Note that FSUIPC7 can also be auto-started with MSFS, but as a separate application.

No, its a simconnect.xml that you need to change, the MaxClients parameter - see https://www.prepar3d.com/SDKv4/sdk/simconnect_api/configuration_files/configuration_files_overview.html. You could also try temporarily changing this line in your ini: TrafficStallTime=1 NormalStallTime=1 to TrafficStallTime=-1 NormalStallTime=-1 This will instruct FSUIPC to just log a message when data is stalled rather than closing the connection and re-connecting (this saving a connection). However, if the connections really are closed, then you will stop receiving data. With this change, you can checj your logs after a session and see if the data was stalled at all during the session. If so, you can determine how long the maximum stall was (with a setting of -1, it will log a message every second that it does not see data), and then set the parameter back to a positive number. i.e. if you find that you were getting a maximum of 3 messages logged, then set the NormalStallTime to 3 (meaning it will then attempt to re-connect after 3 seconds of not seeing data). But if your maxClients is high enough, you shouldn;t need to do that, so try adjusting MaxClients first.

FSUIPC7 is a completely different product, for MSFS only, and does not replace FSUIPC6. There are no problems having both installed, but you can't run both at the same time. FSUIPC7 is also a stand-alone application (whereas FSUIPC6 and earlier were dlls/library plugins to the FS) and should be installed in its own folder. You can also download and install the unregistered version to check for yourself.

What was it?

Such crashes are usually caused by a corrupt or missing weather file, usually the wxstationlist.bin file. To check this, can you delete this file from your Prepar3D AppData\Roaming\Lockheed Martin\Prepar3D v4 folder (if it is there) and check that it exists under your Prepar3D v4\Weather folder (don't delete that one!).

No. Thats expected - it will get very large. There is no point in posting any log if you haven't experienced the issue yet. And I am certainly not interested in seeing a log that big! To see if its a simconnect issue, you need to search the file to see if there was a simconnect error that occurred at the time you lost control. search for the string 'error' or maybe 'i/o error'. If you find one, then you then search and count the number of client connections/disconnections, as that is known to be an issue. Did you increase the maximum number of clients allowed for SimConnect? Also, check you FSUIPC6.log file to see what errors were reported, and also if there are any messages relating to stalled data or reconnection. You can also count the number of client connection/disconnections logged, to see if that is the issue. If it is, there isn't much you can do except to try and prevent clients re-connecting. Maybe show me your FSUIPC6.ini file to see if we can change the stall-time/reconnect settings to see if that makes a difference.

Its completely normal - each MSFS aircraft seem to log continual events, but different for each aircraft. You can ignore these by using the DontLogThese ini parameter. It can go in the [General] section to apply to all aircraft, and in the [Profile.xxx] section to disable for specific aircraft (better). I mean activating the function that you wish to assign/program in the UI with your mouse, to see what events occur when the COM1s are swapped.

Thats interesting! However, it looks like they are using individual events to update each lvar, no? And some have multiple events. e.g. Does this mean that the events don't take a parameter? Otherwise you could just have event MobiFlight.XMLVAR_Autobrakes_Level and determine the state by the parameter.... I haven't been keeping up on the latest MobiFlight developmets - I'll take a look at the weekend. Thanks for reporting, John

For the A320, there are the additional events provided by Mobiflight (and also the A320 mods). You need to install the Mobiglight WASM module and add event files to FSUIPC7 so that it knows about those events. See and I'm not sure about the B787. Try logging events (in FSUIPC) and swapping the COM1 in the UI to see what event(s) are logged, then try using that (you can also try this in the A320).

You have to have everything at the same privilege level, so if running FSUIPC as admin then you need to run Pilot2ARC as admin. Its better to run everything as non-admin if possible, but that can depend upon where you have installed things.

Thats probably a question you should ask on the SPAD.Next support forums. There is this plugin for Streamdeck for FSUIPC - not sure if it also works for the XL but if not it should be adaptable.:

Probably, but you need to try it and maybe adjust. Yes, 10ms is the default for button repeat. These things vary a lot depending n your computer specs, network latency, programs running, etc so its difficult to advise for a particular configuration. You are better of trying thigs out and adjusting your timings/poll rates so that your system can cope. Maybe try with the defaults first and then increase from there.

I think it should be elapsed time, but you should easily be able to verify by just logging the value.

First, please update to the latest version of FSUIPC6, v6.0.12. You are still using v6.0.0 which is quite old now, and only the latest version is supported. Also, please change to use JoyLetters, by setting the following in both of your FSUIPC7.ini files in the [JoyNames] section: AutoAssignLetters=Yes (not related to your issue but best to set this to prevent problems later if your joystick IDs change) You also didn't activate the required logging in your P3Dv4 test, where you have the problem. So, after updating to the latest version (and have updated your ini as above), please redo the test on P3Dv4 but with Buttons & Keys and Event logging activated. Then show me you FSUIPC6.log and FSUIPC6.ini files from your P3Dv4 installation. No need to show me the P3Dv5 ones if its working there.

No files are moved if you install in a different directory than previously - its up to you to move the files. If there is no FSUIPC7.ini file present in the FUIPC7 installation directory, a default one will be created the first time you run FSUIPC7. We recommend not to install in Programs (or any windows-protected folder) as this can (and has) led to may issues (due to access permissions). Better to install as you originally did (now the default location), or in somewhere like C:\MSFS Add-ons\FSUIPC7, Anyway, glad your problem is now sorted. Cheers, John

You can get the list of MobiFlight events from MobiFlight and create your own file. You can use the ones I posted earlier, but they are quite old by now and so probably not complete. Here they are again, but you are better off either creating your own or maybe someone else will post some files with the later events included: MB1.evtMB2.evt

Sorry, Pete just pointed out that you are using FS2004 and not MSFS, so ignore the above about MSFS and WASM. You should be able to use the FS2004 events, but having never used that I don't know what AP controls are available. I'm not even sure if lua is available in FSUIPC3 (Pete can confirm or not) as I've never used it, but if not then you may have difficulty programming buttons outside of the 32 button limit. John

FSUIPC is device independent, so you can use it with any HID joystick type device. Note that the Honeycomb Bravo has button numbers outside of FSUIPCs 32 button limit. To program the extra buttons, you will need to use a lua script. There is one available for this for the Bravo from here: FSUIPC just access to the events provided by MSFS, together with some additional ones that it adds. There are various events to control autopilot functions, some work in some aircraft and not in others. There is a list of available events generated and stored in your FSUIPC7 documents folder. You just have to try to see what works. There are also additional events/controls that you can use that are provided by the MobiFlight WASM module (together with event files that you add to FSUIPC so that it knows about these events). This adds additional events for the G1000, G3000, GNS530, and KAP140. For details, see and There seem to be plenty of Bravo users using FSUIPC7, so maybe they can help or advise on how to configure the Bravo for a specific aircraft. But is should be no different configuring it compared to any other autopilot or button box - to FSUIPC its just a collection of buttons and axes John

You can assign to Electrical Circuit Toggle with a parameter of 46, and this will toggle between Off to left, and with a parameter of 45 to toggle from off to right. However, switching direct from left to right (or vica versa) is more problematic. If its on left, you have to send initially with a parameter of 45, and then with a parameter of 46 - when sending this second parameter it will then switch directly from right to left. I've also looked to see if there is an offset that holds the current setting, but couldn't find one. This should be (I think) either in offset 0x2F58 (FUEL SELECTED TRANSFER MODE), or in 0x0AF8 (FUEL TANL SELECTOR), but the former doesn't seem to change (it holds a value of 5 for me...), and the latter holds a value of 19 on start-up, which is 'Left main', event though the fuel crossfeed is initially off. Changing these values also has no affect. But as the fuel transfer is a three position switch (i.e. left - off-right, which would equate to 2 buttons), how to you propose to manage this with one button? You could manage the two states (left/right) with one button if there was an offset that held the current position (by using offset conditions on your assignments), but you wouldn't be able to set to the off position doing that. Another possibility would be to use the generic triple use lua script for buttons (see the Contributions section), which would, for example, allow you to program a double press for Off, and a single press to switch between left and right. However, you would still need an offset to hold the current value/status, which doesn't seem possible at the moment. There doesn't seem to be an lvar that holds this either. I'll ask on the Asobo forums if why those simvars aren't being updated on the CJ4, or if there is anything else that can be used instead. John