John Dowson

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

Yes, that is what I was referring to. Ok. You can try but I'm afraid that if it doesn't work then it will be a problem with the implementation in the Add-on aircraft. If it doesn't bind in MSFS, then it probably won't via SimConnect/FSUIPC, but you can try. On a similar note, it maybe be worth reviewing this support request regarding the CRS course knob: John

Are you aware of what causes the heading bug incr/decr issue? FSUIPC can get around this, but you need to be aware of what causes this to prevent. I can supply more information if needed. Try and let me know if you need any further help. John

I've generated one anyway. Drop the attached key file into your installation folder: FSUIPC7.key Note that the installer will not validate this license as it currently cannot handle time-limited license validation. John P.S. I will change the title of this post to make it clearer for other users....

I understand your point. There isn't really a 'trial' version of FSUIPC. There's just one version, and the facilities available depend on whether it is registered or not (i.e. has a valid license). I can supply a time-limited license. I've been thinking of doing this for a while, maybe for every other 10 days or so and making it available via www.fsuipc.com. But, to be honest, its just the extra effort of maintaining this over a long period that prevents me from doing this. For now, I don't mind supplying time-limited license on request. Do you want one? John

@woolybugger You posted the entire email, including the key!!!! NEVER POST YOUR KEY IN A PUBLIC FORUM I have deleted your post. If you do that again, it will be banned. As I said, please provide your order number and date of purchase ONLY. John

Presumably you purchased the correct version of FSUIPC (FSUIPC4 for FSX)? If so, please let us know the order number and date of purchase and we can check your details. John

I still don't know what you mean by this! It would help if you could explain what you are doing and what you are seeing, and what the actual problem is. As far as FSUIPC is concerned, a button is a button, the direction doesn't matter. Various rotaries work in different ways with a different number of buttons. For example, the rotaries on my GF panels are 4 button rotaries, two buttons in each direction, one for slow movement and one for fast, so that they can be programmed/assigned distinctly (i.e. for small or large increments on whatever it is controlling). But, as I have said, what exactly is you issue? Are you saying that the button numbers are the same regardless of the direction that you turn the rotary? And that this is only in FSUIPC6, but is ok in FSUIPC4?

@Ross McDonagh FYI, I have also identified an issue where axis can be lost when adding an aircraft to an existing profile. See this support request for further details: This has been corrected in the attached version, so please try with this: FSUIPC6.dll John

Not sure what you mean by this... Some rotaries have two buttons in each direction - one for a small increments and another for larger increments. But what exactly is you issue? If you turn you rotary, you thrn get a button number - can't you then assign to it? Or are you saying that the button number changes when you are not turning the rotary? if so, that sounds like a dirty connection. You can ignore such inputs by using the IgnoreThese ini parameter (see Advanced User manual). I will be adding a button to the UI for this, but haven't got around to this so far.... John

This should be fixed in the attached version: FSUIPC6.dll