John Dowson

As the name implies, it decrements a signed word offset value, i.e. whatever the specified offset holds, it will decrement that value by the defined amount (down to the optionally defined minimum). Not that control, no. But the offset you provide is the elevator trim axis. Yes of course. Its a general control, you have to give the offset as well as the decrement value. Did you not follow the provided instructions? I'm sorry but I can't make them any clearer. It is a utility that you run on a client machine (i.e. not the same machine as the flight simulator) that enables FSUIPC client applications to communicate to FSUIPC on the FS machine. So. basically you use it to move FSUIPC clients off of the flight sim PC to another PC. No, it shouldn't. No, sorry, I can't - far too busy. Extensive documentation is provided and there is a wealth of information on the web. You can also take a look at the forums here, and maybe the FAQ section and User Contributions, which contain useful things that people have done and made available. John

Yes, that matters. If you are running them as admin, you will have to run FSUIPC6/P3Dv5.1 as admin. Error 740 indicates that you don't have the required privileges to run. I'm surprised that it works for 4.5 though - do you run that as admin but 5.1 not?

@GPan099 Could you try the attached version please. I've added back the Alt modifier. However, it doesn't seem to be 100% reliable. Looks to be an issue with MSFS not receiving the input events on occasion, but I'm not sure why. I'll investigate further and report to Asobo if the issue is on their side. FSUIPC7.exe

Looks ok. Could you attach your FSUIPC6.log file please - there should be errors logged there if there are problems starting your [Programs].

No, there is still no way to detect this as far as I'm aware. As there are several other pause states that are detectable (and controllable), use those instead for the time being. John

Yes, of course it is still available. Please see the Advanced User Guide, section 'Programs: facilities to load and run additional programs' (on p44). John

Sorry, what is 'GIT'? Is this an issue with MSFS and not FSUIPC7? i.e. if you run FSUIPC7 without MSFS, are all your devices detectable and useable? If so, I think you need to raise a zendesk ticket with MSFS. I use 6 GF devices without issue.

I think this would be a useful update and will look into it at some point when time permits. John

This is usually due to your device/axis being register in windows as a digital (on/off) device rather than analogue. Please see:

The default hot key for this is Alt+F. Its mentioned in the included README.txt, and on page 5 of the FSUIPC7 User Guide: John

This is described in the User Guide, p6: John

Your macro definition is not correct. Please see the Advanced User Guide, P39: Given that, try: 1=L:ATR42_NEEDLE_ASI_BUG=Set,170 John

@grigna Thanks for the info. However, note that you can also assign your buttons/switches directly to those controls in the assignments panel (with the correct parameter) if you don't want to use lua.

@RISCfuture You can also find detailed instructions in this post: John

Ok. Then please wait for the next release - I will add back in the use of the ALT modifier key. I'll post again here when I have a release for you to test. John

The next SDK update has some corrections (and updated documentation) on the MSFS key input events, so I will revise FSUIPC7's key handling when this is released. I'll see if I can also add back in the ALT key modifier so that the default MSFS key assignments can be used.

Sorry, what does this mean? Are you talking about assignments in FSUIPC7 or MSFS? If the former, all your assignments are stored in your FSUIPV7.omo file. For the latter, I presume that MSFS assignments are stored in a config file somewhere, although I don't know where. I wouldn't ascise changing this file manully though. There are many assignments that you can make in the sim but for which no events/controls are available via simconnect, upon which FSUIPC7 relies. If there is no control that suits your needs, you will have to do as advised above for the cabin lights, i.e. assign a different keypress to the Alt+C function (not using ALT modifier) in MSFS and then assign your button/switch to that keypress in FSUIPC7. Alternatively, if you are looking for a control to open the catering doors, you could try using the control TOGGLE_AIRCRAFT_EXIT_FAST to se if there is a parameter that works for that control for the catering doors.

I checked this in the C208 and it works as expected, although i found that I had to use an increment/decrement value of around 500. You should really try this again as it would be a better solution to overloading your button presses. If you have any issues, let me know which aircraft you are using and I'll take a look. John

@f-111sim Hi Rod, sorry for the delay, there were a few added complications... Please try the attached dll. I've cleaned-up the recognition of axes controls and added several new axis controls, including the ones you requested. The axes are functioning in that they are being sent to the FS, although I cannot confirm if working correctly or not as I'm not sure what those axes are supposed to do...! Please let me know if this is working for you. I have a few other updates (mainly documentation) to add and once done I'll release this version officially. John FSUIPC6.dll

The standard way would be to use the Toggle Cabin Lights control (or toggle bit 9 in offset 0D0C). However, this event/control doesn't seem to be working at the moment. The default ALT-L key press uses the TOGGLE FLASHLIGHT control which isn't available via simconnect, and you can't send this key press combination as the ALT modifier is not supported in SimConnect. Therefore, to assign this to a button or switch in FSUIPC, you would have to assign another known keypress (without using the ALT modifier) within MSFS to TOGGLE FLASHLIGHT, and then assign your button/switch to that keypress in FSUIPC.

Maybe you can check what event this is using (by activating logging for events (non-axis controls)), and compare to that produced by v5 or v4, as well as comparing to what occurs when you try this through your software. From what you are saying, it does seem like a change in 5.1. I'm surprised you are using the ' FSX 747-400, original panel' - did you copy this across from FSX and install into P3D? I have FSX-SE still installed somewhere, I can try adding that to my P3D installations (now only 4.5 & 5.1 though) to see if something has changed, but this would take me a while. I probably won't have time to do this for a few weeks with my current backlog, so may be better if you can investigate this and report back for the time being. John

Have you tried looking at the NAV1/2 flags in 0C4B / 0C5B to see which is active? Maybe in combination with the localiser/VOR flag in 0C4D / 0C70....

Btw, are you using GeForce Experence? If so, try de-activating the in-game overlay. Or if you are using MSI Afterburner or RivaRuner, try disabling those.

Just checked you logs and ini and they look good - no more registry issues or warnings, so it looks good to me. And all is detected correctly in your Joyscan.csv file. Let me know if you get any further issues.

I think the FSLabs Axxx series of aircraft have re-purposed the rotor brake control with various parameters for different functions. There is plenty of information on how to use these aircraft with FSUIPC over on the fslabs forums.