John Dowson

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

When you turn the encoder, you should see the "button number" (as well as the device number) for the rotary in that direction. You will only see an "offset" if you already have an offset assignment to that button. Sorry, I don't understand what you mean by this. Can you explain? Also, please attach your FSUIPC7.ini file so I can see your assignments.

This error is mention in the included README.txt, and there are many other support requests asking the same question..... You need to (re-)install the VC++ redistributables. Check the README.txt or other support requests for details.

Yes, sorry for not replying sooner. This error is also mentioned in the included README.txt, and there are several support requests already on this error. Please remember to check the documentation and search for similar problems before you post in future. Thanks, John

There was an issue with losing axis prior to 6.0.11 which I corrected, but it seems that there is still something amiss in 6.0.11. I'm looking into it. John

Hi Sergio, I've had a few similar reports recently but haven't been able to reproduce so far, and the other users who reported also couldn't reproduce. Could you tell me exactly what you did to make the new livery profile specific and I'll see if I can reproduce. Thanks, John

In your installation folder, the same location as the log file and the FSUIPC4.dll.

Hi Gary, What exactly isn't working? Your log shows your 4 devices acquired ok, and you have various assignments that should work. The log also shows you loaded the Bonanza G36, for which you have no profile set-up, so it will just use the default (general) profile. Looking at your ini, you have your throttle, PropPitch and Mixture axes set-up in the general Axes section (i.e. your throttle axes) , but no elevator, aileron or rudder. In fact, you do not have these axes (yoke) assigned anywhere (i.e. in any profile) - do you have these set-up in MSFS? Are the assignments you have working ok, i.e. the throttle should work in all aircraft - does it? You have also assigned your axes to 'Direct to FSUIPC Calibration' but have not calibrated your axes. You should really do this - see the User guide for details. Maybe you could calibrate your axes and tell me in more detail what isn't working. Can you see each of your devices axes/buttons in the FSUIPC assignments windows? You could also activate button and event logging (and later axes) and operate some buttons to see what is logged. John

Yes. But of course you can always place it over the sim window... I've attached two lua scripts that display the frame rate, one using the standard lua ipc.display function (that uses SimConnect_Text under the covers) and another that uses the Wnd library. Due to the issues with the SimConnect_Text function, the ipc.display version has various issues (although works fine in P3D). John FPS_Monitor.lua FPS_MonitorW.lua

FSUIPC uses the SimConnect_Text function for displaying text. There are currently many issues with this - from the MSFS SK: There are also problems with updating text in a simconnect text window (multiple windows are created) and the 'time to display'.. For these reasons, I have added the lua Wnd library which can be used instead. This displays the text in a separate (moveable and resizeable) window. To display text without lua, you can use offset 0x32FA, but this uses the SimConnet_Text function and so suffers from the same issues as the lua text display functions. If you are writing your own program, you could also use the SimConnect SDK directly rather than using one of the FSUIPC SDKs. No, this is not possible. John

Hi Gary, Something must have changed! What Logitech/Saitek panels are you using? Are you also using spad or spad.next? Could you show me/attach your FSUIPC7.ini and FSUIPC7.log files please. John