John Dowson

Yes, as Pete said, there is something strange in your installation. However, as you selected the P3Dv4 directory when you installed FSUIPC5, this is the directory that should have been used, so there is also an issue in the FSUIPC5 installer that I will look into. As the original problem is your P3Dv4 installation, it would be better going forward for you first to correct that, then you can re-run the FSUIPC installer to install to the correct place. I will be releasing a new version later this week (5.152), so I'll correct this installer problem before I release. John

Hi Luke, I was investigating this for you, but unfortunately I broke my foot (3 metatarsals) around 5 weeks ago so things have been moving along quite slowly. Its not a problem extracting the viewpoint for you, and then changing this to the correct reference frame, but in my investigations so far I'm only getting the initial viewpoint value from P3D and this doesn't seem to be updated when you change the viewpoint (with the standard P3D key controls). I therefore need to investigate more and possibly raise with LM, so this may take a while. I'll keep you informed. Cheers, John

The earlier versions (FS4, FSX and P3D1-3) used hooks into the actual code to trap the mouse click. In P3Dv4 this is no longer necessary as LM provide facilities as part of its Programmer Development Kit (PDK). Makes the code in FSUIPC much simpler and more foolproof. So mouse macros will not work in non C/C++ SDK Guages in FS4, FSX and P3D1-3. John

That does look strange. I'll look into it and get back you. John

Hi David, I am not saying that you need to buy a new license! If you need FSUIPC4 then you obviously need a license for FSUIPC4, not FSUIPC5. I was just pointing out that FSUIPC4 and FSUIPC5 are different products and require different licenses. If you already have a license for FSUIPC4 then use that. John

All 3 components (name, email, key) must be exactly as specified in your purchase email from SimMarket - please cut and paste from there. If your current licence is for FSUIPC4, then you will need to purchase a new license for FSUIPC5. Your address is with SimMarket and can be updated from our SimMarket account. Please do not post or attach any key details - I have removed them for you. John

I'm not sure this is needed.... Can you not use the 'Ignore Axis' button (top right) in the Axis Assignment tab?

Hi Masterius, they will be used (ie re-purposed for internal use) by your add-on aircraft or Accu-Sim - I also get them with A2A's Cherokee (with Accu-Sim). Just ignore them. You can add the following to the '[General]' section your FSUIPC4.ini file so that these are ignored: DontLogThese=66507,66508 John

Yes, its currently only available for buttons, but I can look into extending this functionality to axis as well.

If Linda works fine, why not use that? Does FSUIPC see your knobs/buttons (i.e. are they recognised in the buttons & switches assignment tab)? Are you using VRInsight drivers or software?

You really need to configure (assign & calibrate) this yourself - check the user manuals provided. If you want something off-the-shelf for the AS Airbus then maybe take a look at Linda.

We provide (or at least try to...) all the information that you should need in the manuals, so please use them. If you have any issues/problems, then post and we can help (but check FAQ and previous posts first).

Ok, so FSUIPC is not loading, and so I will need to see you simconnect log file to determine why, so you need to sort out access to your documents folder. Are you sure that you are accessing it from the correct place? Try from the Libraries -> Documents -> My Documents quick-access link in explorer. I can see on my windows 7 system that I have 2 'My Documents' folders (well, one is a link) for some reason, and one (the link) also gives me an access denied error.

Hi Akis, to do this, you would have to use your lua script to receive the axis values and send on the axis controls. What you need is a lua script to receive your axis values and then send the controls depending upon the state of a flag, also controlled using your button. In your Axis Assignment tab, you need to assign your axis to 'Send to FS as normal axis', and then select the 'LuaValue <your script name>' option. This will send the axis value to a lua variable called ipcPARAM, which you can then optionally use to send the control to the sim, depending upon the state of your button. The lua script should be auto-started (i.e. add it to the '[Auto]' section of your ini. Check the documentation for 'event.param' on page 29 of the Lua Library documentation. Not sure why you would want to do this though.... Cheers, John

Your FSUIPC4.log file should be in your Modules folder :C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.log

Hi. That looks fine. I'm not sure why FSUIPC cannot find it - was it in the location I gave? Presuming you have actually ran your current P3D version at least one, could you first try running the installer again. If it fails again, you can try manually adding the following xml to the bottom (before '</SimBase.Document>') of you dll.xml file: <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>E:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL</Path> </Launch.Addon> John

FSUIPC4.log file please? Also, a simconnect log file - please see this post in order to activate this:

Your install log looks ok. Do you have an FSUIPC4.log file in your modules folder? If so, can you please post/attach.

Sounds like your DLL.xml file is corrupt - can you please post it and I'll take a look. It should be in C:\Users\kai-r\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.XML. You also posted in the wrong place - I've moved your post to the support forum.

Your dll.xml looks fine. Could you post or attach your FSUIPC install log please.

The SDK is the 'Software Development Kit', which allows you to write programs (in various languages) that communicate with FSUIPC (i.e. read/write offsets). The changes did not allow you to see the throttles! They only put back your previous assignments/calibration to that device. If that worked, then you must have been able to see this before, they just weren't assigned. Well, what you have now is all your old assignments back from your old ini, or thats what I thought! Looking at your ini, it looks like you have your flaps and toe brakes calibrated: LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16 FlapStarts=-16384,-13765,-9239,-6209,-2020,336,6755,10375,11868 Flaps=-16384,16380 FlapEnds=-14027,-10025,-7032,-3553,75,4292,10226,11607,13137 But no calibration for your ailerons, elevator, throttle, etc, so you will need to calibrate them (especially if you are sending to FSUIPC for calibration). Then again, if you are going to upgrade ProSim, you will probably be better off assigning and calibrating there, as Pete suggested. It is recommended to run on the flight sim pc to avoid delays caused by network latency, although it should still work running on the slave.

Your joyscan.csv file shows the device BU0836A Interface is recognised and matches you log and ini, so this must be your throttle device - please go ahead and make the suggested changes. I'm not sure if this will work though, as you cannot see the axis value change (in the axis assignment tab) when this is unassigned, which is strange. You could also try downloading the HiDScanner utility - from Run this and move the throttle to see if any axis values are changed (and post the log).

As you can see if you read this thread, we do not support XPlane / XPUIPC - that is a different product to FSUIPC and by a different author. Please use their support. John

3 weeks? You should have posted earlier!! Basically your problem is that you installed P3D in the default 'Program Files' directory, which is restricted by windows. Always better to install in a different (and unrestricted) folder/directory. Installing FSUIPC does try to set the permissions to allow this, but for some reason this sometimes fails on Windows 10 - you may find that you have an error in your install log for this. Rather than running as n admin, you can manually give permissions to 'Everyone' to the Modules folder. I will be releasing a new installer at some point this year which will allow you to choose the xml add-on install method instead and so allow installation of FSUIPC outside of the main P3D folder. John

Are you using external USB hubs, and if so the same ones the different PCs?