John Dowson

Could you attach your original/backup ini file please. If its too big, you can try zipping/compressing.

Hi Sunny, please post/attach your latest FSUIPC log and ini files, and also your joyscan.csv files (all in your Modules folder), and I'll let you know how to update... John

there is nothing in the log as you need to select 'Normal log file'. Please check that option. 3AE8 is also a float64 (FLT64), and 3A28 also as a float64 only. I don't know why its not updating the 088c value though in the FS/simconnect display window. Could you maybe try also with a default aircraft? John

You can just use the 'Export' facility from regedit....

I assumed it was a typo! So the key is correct but the value wrong. Change it from 'F:' to 'F:\P3Dv4\'.

I have correct registry entries for P3Dv4.5HF1.....no point showing you my value though, as I have it installed in a different place....

Oh - you may want to make a copy of your key and ini files from your old Modules directory (if you have them), and drop them into the new one once FSUIPC5 is installed, or just rename your f:\Modules folder (rather than delete) so that you still have access to them, if needed.

You could try editing your registry. Make sure you take a back-up first. Then: Ignore this. Presume 'StuPath' is an error? Anyway, change so that you have SetupPath set to 'F:\P3Dv4\' Thats ok. You will also need to remove and re-install FSUIPC. To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder. If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file. Alternatively, maybe uninstalling and then re-installing the P3Dv4 client may correct your registry for you, but I'm not sure on this. Let me know if you have any issues. John

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: