John Dowson

Hi Paul, first, its probably MSFS crashing, not FSUIPC7. If FSUIPC7 crashes, it should not affect MSFS as its running in a separate process. To verify this, you can uncheck the option 'Exit with FS', and then FSUIPC7 should remain running when MSFS crashes. Also, the log file should show FSUIPC7 exiting normally if MSFS crashes, as it will just lose the connection and exit gracefully. When MSFS crashes, you should also check the Windows event viewer to see if there is a crash log. if so, you need to raise a support request with Asobo/MSFS via zendesk, and include the crash report from the event viewer. John

Thats interesting as most people find that the increments/decrements are too small and need to increase them! However, the procedure is the same. You can use offset 0x0BC0 with the Offset Sword Increment/decrement controls to specify the granularity you require, as explained in this post: John

Hi Hermann, I'll take a look. Is this a general problem for all aircraft or for a specific aircraft? John

@jockoflocko Sorry for the late reply. I see you have worked out the issue - you have to be 'ready-to-fly' to be able to calibrate the axis, not just connected to the sim. I'll think of adding a pop-up message/warning (or maybe disable the calibration tab) when not in the correct state, to make it a bit clearer. John

What happens when you click 'Yes' to run?

First, you are not using the latest version of MSFS - can you please update to v.7.0.3. Only the latest version is supported. If it still crashes, can you provide more information - as well as the event log, can you attach you FSUIPC7.log and FSUIPC7.ini files and provide a brief description of what was happening when the crash occurred. Thanks, John

It IS there. Pete posted the contents - if you see something different then please post a screenshot so that we can see what you can. If you are not seeing the extensions, it is because of your Explorer view settings, but the files should be there non the less. We need this information from you to help you.... 32/64 bit is mentioned. Win versions are only mentioned when applicable. John P.S. Another possibility is that you have some antivirus software running that is removing/quarantining the exe. So check your antivirus settings/history.

I'm afraid I'm not that familiar with such issues - I'm a software guy and defer to others when it comes to most hardware issues - maybe @Pete Dowson or @Thomas Richter can help with this. I don't see how the rotary can fire different buttons between win 7 and win10 un less its a driver issue, but maybe Pete or Thomas can explain this. Regards, John

Yes, This was a problem previously reported that we raised with Asobo, but I added a temporary fix so that previous assignments would still work. When Asobo fix such issues, there is no feedback from them so we rely on user reports such as yours so that we can remove such corrections!. Hopefully there aren't too many hacks like this that need reversing, but due to my failure in properly tracking such issues, I'm afraid we rely on user feedback to correct. Thanks and regards, John

Ok, no problem. Thanks for reporting back. John

Hi Dennhy, I'm glad this is now working for you (with the key file I PM'ed you), but I am still perplexed as to why you couldn't validate and generate the key file via the FSUIPC4 installer. John

I've been testing the new dll this morning and it seems fine here, so could you try again please and let me know, and supply the information requested if it is still crashing. Thanks, John

Just FYI, this is a known MSFS issue with certain controllers. See https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 John

Then this does sound like an issue with the aircraft that should be reported to the aircraft developers. You could maybe try first sending a Heading Slot Index Set control with parameter 1 to see if that gives authority back to the HSI but I doubt it (as this is usually only needed to switch authority to/from the FCU). If you log events (using FSUIPC), can you see any events at all when you rotate the knob in the UI? Do you see the standard VOR1_OBI_INC/DEC events, something else or nothing?

Don't - but make sure you calibrate your axes and define an appropriate null zone. John

Hi Gary, Sorry, I know nothing about those FIP gauges - you should certainly contact the developer for support. Cheers, John

Most axes don't centre at exactly zero. This is why you have a null zone around the centre which you set-up during calibration. I have MFG Crosswinds and this is my rudder calibration entry: Rudder=-16384,-650,650,15648 i.e. a null zone between -650 - + 650. John

There is an AUTOBRAKES ACTIVE simulator variable, but it looks like this isn't exposed via SimConnect at the moment. I'll check it to see if its available (in case its just missing from the SimConnect documentation) and if so I will add it and let you know. In the mean-time, you could see if the standard brake indicator offset 0x32F9 show anything for Autobrakes.. There is also a simvar LIGHT BRAKE ON which is available via SimConnect, which is True if the light brake is on, but this may be for toe brakes. I'll add it anyway so you can check. It may take me a few days to get around to this though. John

That is strange, and worrying. The fix for this was minor and could not cause this, but there are a few other minor updates also in that version. I'll take a look, but would be useful if you could show me a log file after a crash, and also check to see if there is a crash log in the windows event viewer and if so paste the details. Thanks, John

So this is the case. It sounds like this is either a problem with the rotary or the driver. FSUIPC is only reporting what it sees from the windows joystick HID API. Maybe you can check what windows sees under game controllers for that rotary? What is strange is that you say this was working fine under win 7. What button numbers did it report there in each direction?

The documentation is installed under your Windows documents folder, as explained in that manual. The documentation is only installed in the install location if this location cannot be determined or accessed: Time-limited licenses are not validated by the installer. Just download the key file and drop that into your installation folder. I will amend the post above to make this clear. John

Hi Gary, thanks for reporting back and your kind words. Regards, John

If you still can't get this working, maybe you can try running FSX with an unregistered version of FSUIPC to see if it works with an unregistered version. If not, it may be due to your VS redistributables. I have had cases in FSUIPC7 where an issue with the VC redistributables causes an issue with registration (and this issue also prevents an unregistered version of FSUIPC running, hence the test), but have not heard of this issue in FSUIPC4... John

Its not just the key code that needs to be entered correctly. but all details, as specified in the email (that you posted earlier). They have been validated and are ok, so it must be that you are not entering them correctly. Please try again, and paste each field (Name, Email/Address, Key) exactly as specified.

But shouldn't the HSI be slaved to the VOR? Or is this what the problem is with the Carenado? It may be something that, in the add-on aircraft, is separated and only controlled by lvars (local panel/gauge variables). Currently no lvar access in FSUIPC at the moment, but Im looking into it. John