John Dowson

Did you try running FSUIPC7 after doing this? It shouldn't uninstall earlier versions.... It shouldn't make a difference installing individually oir installing the combo pack (if installing the correct versions). If its still not working, uninstall 2015, 2017 and 2019 and try again with the combo pack.

You go into the windows settings, select Apps, and uninstall from there.:

WideFS is a separate product - you do not get a key for WideFS7 when purchasing FSUIPC7. Yes, its a different product. If you previously purchased WideFS7, your key is still valid. You can retrieve it from your SimMarket account. It has never been 'included' with FSUIPC, although I think that there may have been a bundle offer where you could purchase FSUIPC + WideFS together for a discount on the total individual price. John

As before, check the SDK. There are no key input events for those keys. The > is mapped, but to 0x6E (with a shift), so I could add a similar hack to get this key working. The < results in no events, so I can't do anything with that. But I really don't want to start hacking for individual keys. You should restrict your assignments to those keys available. John

Yes - FSUIPC recognises the modifier keys directly from the windows API and doesn't use SimConnect key input events for these. John

Its from mobiflight. FSUIPC nly has one offset for each gear wheel which gives the deflection as a percentage. Presumably its just the gear left/center/right position offsets that you have already mentioned. Try monitoring them to see how they change when you retract or extract the landing gear. I would have thought that a value of 0/100 would be retracted/fully extracted (or vice versa) and a value in between would be when it is extracting or retracting. Ok, good. A full list of events is generated by FSUIPC7 and placed in your Documents/FSUIPC7 folder when you run FSUIPC7, called Controls List for MSFS Build 999.txt (999 is the current minor build number). The MSFS documentation is in the SDK - you need to download and install the SDK to access the documentation. If you want to do this, see https://forums.flightsimulator.com/t/how-to-getting-started-with-the-sdk-dev-mode/123241 John P.S. The offsetStatus spreadsheet also lists the simulator variables used for each offset (in column G), where appropriate, and at the end also contains a list of other available simulator variables currently not requested.

Do not delete, but uninstall. Yes, but uninstall 2017 not delete. When you uninstall or install, it applies to both versions. You probably also need the 2019 versions, which should be installed after the 2017. Its not that difficult - they just need to be installed in the correct order. As you have the 2017 installed and not the 2015, you have to uninstall the 2017 before installing the 2015, and then re-install the 2017 after you have installed the 2015. No - why would you want to do this?

Sorry, of course you are using FSUIPC6 and not FSUIPC7.

I can find nothing in the SDK (in events or simulator variables) that relate to the HotBrake or TerrON, and also nothing related to these in the MSFS assignments. Therefore its not currently possible to control these. John

Sorry, I don't understand what you are saying or trying to do here. The offsets you mention hold the gear left/centre/right position. What do you mean by 'extracted' and 'moving'? What are you actually trying to achieve? If the autobrake offset you are using is 0x2F80, this is documented as 'No longer writeable' (in the offset status spreadsheet) I've checked the code and it seems that this was disabled as the Set Autobrake Control was not present in earlier versions of the SDK. As its now available, I will re-activate that offset for writing. What are those? Is there anything in MSFS that you can use to control these? Please try the attached version c7.0.3c where I have re-enabled offset 0x2F80 for writing. John FSUIPC7.exe

@zorzini I am wondering whether this could be the same MSFS bug explained here: https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 John

Did you get this working? It does seem top be an MSFS bug - see https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 John

@ark1320 Thomas has pointed out we are actually receiving the arrow key key presses via SimConnect, but we are receiving these as numpad key events. As they are being received, I can check the state of the arrow keys when the notification is received and re-map to the correct VK code. I've done this in the attached version if you would like to try: FSUIPC7.exe John

But remember, the SimConnect API dates back many years, and maybe these keys were not common then. Or maybe they are covered by some of the other VK codes (but I would expect VK_LEFT, etc, or VK_0x25, etc which don't seem to exist). But really, you need to address such questions to Asobo. Well, if they are not assignable I'd rather remove them completely. Or is it worth keeping such key assignments as they do have an effect when FSUIPC7 has the focus? I think the former. But, as the SDK is still under development, for the time being I think its better to accept all and provide a reference to what actually works in SimConnect in the manuals. Once we get to SDK 1.0, I can consider updating the manuals (and maybe the code) to then reflect what is actually assignable. John

Hi Alain, what have you tried? What is the problem? Which VRI insight device overhead? Have you read Appendix 3 in the Advanced user manual (Handling VRInsight serial devices in FSUIPC)? Or is your device recognised as a standard windows hid joystick device? I'm sorry, but your question is so general its hard to answer. Please read the documentation, especially that annex in the Advanced User guide, and the separate document on VRInsight devices (Lua Plugins for VRInsight Devices.pdf). If you still have issues, then please post again (please check for previous posts first) and provide more details on what your actual problem is. John

You logs don't show anything and are huge. Please de-activate most of the logging options when you supply a log, and only activate those relevant to your issue (or what we advise) - which in this case would be axis logging. However, looking at you ini, you have your aileron and elevator assigned to direct to FSUIPC calibration, but your calibration looks very strange: For your elevator, your null zone is bigger than your axis range! For comparison, this is what mine looks like: I suggest that you try to re-calibrate your axes. Please se the provided documentation on how to do this. You may also want to go into the windows joystick calibration page, and make sure they are calibrated in windows correctly first. John

Just looked at this in the A320Neo (but without the FBW mod). In the default A320, both of the seatbelt and smoking switches are inoperative. You can send the relevant controls (Cabin No Smoking / Seatbelt Alert Switch Toggle) and the offset (and associated simvar) gets updated, but has no effect on the aircraft. It therefore seems that this is not connected yet. I'm not sure if the FBW mod is supposed to correct this as I haven't used this (yet!). John

But, as I said, it isn't a bug so no fix is required. Its a new feature request that is needed, as the arrow key input has never been available via Simconnect. Previous versions of FSUIPC were an embedded dll and so could receive all keystrokes natively (i.e. using the windows API) and did not rely on SimConnect for this. Now FSUIPC7 is an executable, it can only get the keyboard events (when MSFS has the focus) via SimConnect. Again, check the SDK documentation to see what keys are available. Well, its the same effect/result, but the issue is different. The issue with the numpad keys was due to a defective SDK (and documentation) and a hacked implementation in FSUIPC7 due to this. This was rectified in the 0.8.0.0 SDK release and the v7.0.2 release of FSUIPC7. The issue with the arrow keys is that they have never (and most likely won't) been made available via SimConnect. I will update the documentation to make this clear, and think about removing these other keys from FSUIPC7 as there is really no point assigning to such keys. John

Hi Al, there are no key strings listed for those keys yet in the SDK, so I don't think they are even planning to provide support for them at the moment. In fact, looking at the P3D SDK, they are not even available there, so it seems like these keys have never been available via SimConnect input events. John

@pilotjohn Can you try the attached version please (v7.0.3a). In this version, I have added read/writeable offsets for aileron slope: 0x08A2 elevator slope: 0x08A3 rudder slope: 0x8A4 steering tiller slope: 0x8A5 Each is a signed byte (SB). Only values in the range -15 to +15 are accepted (values outside will be capped to that range). Also, at the moment, you can log the slope adjustments made by activating Extras logging. I probably won't keep this in the final version - or I'll keep it but move it to a different logging flag, still undecided.... Let me know if this works for you. John FSUIPC7.exe P.S. One thing you should be aware of: if you are changing the slope dynamically, it won't be saved for the next session. However, if you go into the axis assignments and calibration dialog , when you close the dialog any current active slope will be written to your FSUIPC7.ini.

It doesn't matter where its located - it uses the registry to determine the previous installation location. It cannot determine the previous installation location if you manually uninstall FSUIPC7 first (by using the provided/generated uninstallers), or if your beta version was very old, before I added the installer. For future reference, when you install future versions/updates, if you just run the installer (without uninstalling first) and accept all the default values, it will update the current installation and preserve all your settings. John

I'm not sure where you read that.... Whenever you install FSUIPC7, if the installer detects that FSUIPC7 is already installed, then it will automatically uninstall the current version and then use the same defaults (for installation folder) as your previous installation. If you don't change this and install in the same place, then all your settings will be preserved. If you select to install into a different folder, then to preserve your settings you will have to copy across the FSUIPC7.in file together with any auxiliary files (eg. .lua, .mcro, .dll, etc) that you may use. John

To control the trim wheel sensitivity, try the solution mentioned in this post: And please read the Installation and Registration guide, which will tell you where everything is installed. John

If there are no lvars, you can check if there is a custom control you can use instead - sorry, don't have the PMDG 737 so I'm not sure what custom controls are available. Otherwise, yes, try using a mouse macro... But why are you looking at the log to create a mouse macro? You don't need to look at the log to create a mouse macro, or to then assign the macro to a button. I see Pete has also just replied.... John

The '-FastLaunch' option is automatically added to start MSFS store installed versions, but I don't think this is possible with the steam version as a command line parameter. To use this option with steam, open your library in Steam, right-click on MSFS and select Properties. Under the General tab, click SET LAUNCH OPTIONS, then enter -FastLaunch in the pop-up dialog. John