John Dowson

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

I did a few tests this morning, and found that its more responsive if I assign Direct to FSUIPC calibration and use the Steering Tiller control, so switch back to this - but I think you should also disable auto-rudder in MSFS as this may interfere... It still slows slightly during tight turns (but a lot less pronounced than when using MSFSs Steering Set control) and an occasional touch of more power is sometimes needed to keep the aircraft moving. Just did a few circles taxiing on the runway at Heathrow with about 10% power (fixed) without an issue. I took a video from my phone to show you but having difficulties transferring it to my PC - also tried to take a video from the cockpit view using GForce Experience but that didn't seem to work either... There's not much else I can do. I think if the ground steering isn't accurate on the B787, you need to report to Asobo.

You shouldn't need to run FSUIPC as admin, unless maybe you are also running MSFS as admin.... Check that you haven't installed FSUIPC in a windows protected folder (such as Program Files). You should install it in its own folder, outside of the MSFS folders and not under a windows protected folder.

Did you install the MobiFlight WASM module into your MSFS Community folder?

Yes, there is the announcements sub-forum: https://forum.simflight.com/forum/140-announcements/ I'll post there when the beta is ready to be released, and also create a topic in this forum for feedback.

Check to see if your FSUIPC7.ini file is being updated - that is where your assignments are held. It should be located in your FSUIPC7 installation folder, along with your FSUIPC7.log file. Do you see it there? If not, it could be that you installed in a windows protected folder. Try re-installing in a different location of that is the case. However, if you are using a registered version, it should be ok as the FSUIPC7.key file has been created, so I don't know why it wouldn't be able to create or update your FSUIPC7.ini file.

Do you have a steam or MS Store install of MSFS? All the desktop link does is display a splash screen and then start MSFS. You can skip this and start MSFS how you used to before you installed MSFS. Try that and see if MSFS starts and also FSUIPC7.

It is the free version that supports the reading/writing of values to the offset area, accessible by the provided SDKs. The major functionality that a license adds is device/controller assignments and access to the Lua library and interpreter functionality. Best to just download and try the free/unregistered version firt to see if that suits your needs. John

I don't know X-Sim, so not 100% sure what you are asking, but FSUIPC4 is the FSUIPC version for both FSX and FSX-SE.

The logs look ok now. They show a few full -ve tiller deflections and some positive (but only up tp 2/3rds). There are a few rudder axis controls so they must be either from an MSFS assignment or auto-rudder. How was the handling - do you get the same problem? If so, I'm not sure there's much that can be done. Is the handling better using Steering Set or better using FSUIPC's Steering Tiller control? You can switch back to the other control to compare. You could also assign your tiller axis to both the rudder and the steering tiller axis (and turn off auto-rudder) to see if that helps. When did you notice the change in the steering handling? Was this after (or before) the last MSFS update? I'll have a look at the B787 later today to see what works best for me and report back.

As well as what Pete says, you can also activate logging for Buttons & Keys and Events (non-axes controls) and check to see whats happening when you activate the button assigned to your Parking Brakes. You can see this in real-time if you open the log console window, and also attach your FSUIPC6.log file if/when you attach your FSUIPC6.ini.

You loaded a different model of the 787-10 that is not covered by your profile. Please change your '[Profile.Custom B787]' section to the following so that it will match ALL of you B787 variants: Can you also change to use the following parameters in the [General] section: InitialStallTime=125 NormalStallTime=-2 And, as I said, you have to be moving for the steering tiller to take affect (and be logged), so you need to apply some thrust and get moving before you move the tiller through its full axis. Try opening FSUIPC's console window and you can see what is being logged in real time. No, that shouldn't be necessary. Not sure what you mean by this. The tiller won't work if the aircraft speed is below the RudderBlendLowest parameter, which defaults to 1 (knot). Please check your logs before posting them again. We are after a log that shows the rudder axis controls with the parameters, to see if you are getting the full range. There is no point posting the log otherwise. And, as I also said, maybe also try assigning to the FS Steering Set control (and still calibrate in FSUIPC) to use the actual tiller axis rather than the rudder. Yes.

FSUIPC4 is for FSX, not MSFS. For MSFS (2020), you need FSUIPC7. If its FSX (or FSX-SE) that you are using, then your registration details are still valid. Make sure all three parts - name, email/address, key - are exactly as written in your SimMarket purchase email/account. John

Yes, if/when you upgrade and your license fails. It will still validate in the installer, but when you run FSUIPC you will find your assignments have gone as you will be unregistered. When that happens (and if i haven't PM'ed you a new license by then), just comment on this topic again to remind me. John

WifeFS7 is to allow FSUIPC clients to run on a separate PC to that of the FS, but not on a tablet. It runs on the client PC, not on the PC where your Flight Sim is running. It duplicates FSUIPC's class name, so that programs can talk to it as they do FSUIPC. You can run it on the same PC as the FS if you like (only useful to have button-screen functionality on the FS machine), but to do that you have to change the class name it uses via the ini.

Thee control numbers for events in event files are determined as follows: control number = 32768 + (event file index)*256 + event index number where event file index is the index number of the event file (in your FSUIPC7.ini, under [EventFiles]) and event index number is the idex number if the event in the event file. So, the first event in the first event file will have a control number of 32768, the second event 32769, first event in the second file as 33024. etc

Yes - its loaded but won't be added to the add-on menu (and init page displayed) until an aircraft is loaded and you are 'ready-to-fly'. John

That will be needed for the following and subsequent releases.

The mod creates that? Weird.... Why? And if thats automatic, why does that affect your assignments? Surely the mod isn't telling you how to assign or/and configure? Do you have any references for this? Does it help you configure your throttle in FSUIPC, and if so, how?