John Dowson

No hay una version de FSUIPC que funciona con P3Dv4.0. Dime tu numero del pedido.

If you have a license for 4.0, it is free to update to 4.5. If you do not have a license and are using an illegal copy, I cannot help you further.

For FSUIPC6, the documentation is installed in a folder called FSUIPC6, located underneath your windows Documents folder. For other versions of FSUIPC, the documentation is installed in a folder called FSUIPC Documents, under the Modules folder (under your sim installation folder) where FSUIPC is installed.

I need to see your FSUIPC6.log file (from your installation directory), not the installation log. What version of P3D are you using? FSUIPC v6.0.4 is compatible with P3Dv4.1 and later. FSUIPCv6.0.5 has just been released, and this is compatible with P3Dv4.3 and later. If you are on an earlier version of P3D, you should update (its free, so why not!). You should really upgrade to the latest P3Dv4.5 HF. John

Its far easier for me if you attach your log rather than posting pictures! Could it be that something (AI separation?) is trying to move an AI aircraft that has already been removed/deleted? Difficult to tell without the full log.

No recommendations, but any device recognised by windows as a hid device should work with FSUIPC. The Saitek switch panel does not work with FSUIPC as its not a HID device. For this (commonly used) switch panel, there is an additional freeware driver (SPAD) or payware version (SPAD.next) that can be used.

FSUIPC5 is for P3Dv4 only. For FSX, you need FSUIPC4. For the PMDG 747, there is a dedicated offset area. Please see the PMDG documentation provided with FSUIPC (all versions).

Hola Juan, could you try the attached dll please: FSUIPC6.dll Saludos, John

Hi James, could you try the following dll please: FSUIPC6.dll Cheers, John

Hi, could you try the following please: FSUIPC6.dllFSUIPC5.dll Thanks, John

1. I haven't tested vjoy with FSUIPC6 but it should work. If not it will be updated. 2. We advise to disable controllers in P3D if assigning all axis in FSUIPC. The reason for this is that P3D has a tendency to automatically re-assign an axis when recognised that is not already assigned in P3D, which can then cause conflicts with dual assignments. No problems if you are assigning all you axis in P3D. 3. No, sorry. There is the freeware version that allows 3rd party programs to use the offsets to communicate with P3D, but no trial version with assignment functionality. 4. No. FSUIPC6 will work with P3Dv4 and P3Dv5. You will get free upgrades for the life of FSUIPC6. For FSX, you need FSUIPC4 which is a different product.

Sounds like the downloaded file was corrupted somehow. Please download the installer again and re-try. The download is a zip file. When you extract, you should get the installer (an exe file) as well as an installation and registration guide (pdf) and a textfile containing recent changes. Run the exe (windows 10 64-bit).

If you are changing the image definition, it will create a new bitmap and overwrite the existing one. If you want to display/keep multiple bitmaps, you would have to save/rename the original before updating. FSUIPC only provides the facilities to create the bitmap. Sorry, but I do not use Project Magenta and cannot advise further. Have you tried their support? John

FSUIPC6 will be installed in the selected installation directory, not necessarily in the Modules folder. Please see the Installation and Registration guide.

WideFS7 is compatible with FSUIPC6.

I am sorry but I cannot support AIS. I do not have or use this add-on. You could try with Debug=Please LogExtras=x10000 This should log a lot less and may help.

What version of FSUIPC6 are you using? Can you attach you .log file please. John P.S. It seems that this is an issue with LINDA that Andrew is investigating. There is a lot of logging that could be activated, but I'm not sure if this would be useful at this stage. Andrew will let me know if he needs any assistance with this. Make sure you are on the latest FSUIPC6 version though - 6.0.4.

Changes to FSUIPC are listed in the History document. Recent changes that affect AI traffic include - Improvements to AI traffic limiter (v5.152, July 2019) - bug fixed causing a CTD when controlling many aircraft (v5,152, July 2019( - new offsets added for count of ground and airborne AI traffic (v5,152, July 2019) - new "Traffic" tab introduced with additional controls and ini parameters (v5.152, December 2019) - Correction to reading of ZapCylinderAltDiff ini parameter (v5.152, December 2019) - correction to logging of period AI traffic data (v5.155, March 2020) You will need to ask AIS this! You could enable logging of AI data. To do this, add the following to the [General] section of your ini: Debug=Please LogExtras=x40000 Be warned though. This will produce HUGE logs. May be better to enable when well away from busy airports but are still getting a few updates that exhibit your problem. To enable it in the Sim, leave the "Debug=Please" set in the INI file, but not the LogExtras= line. Then, to turn it on, go to FSUIPC options, Logging tab, and enter 262144 in the Extras edit box, near bottom left. (262144 is the same as x40000 but in decimal because that edit box won't accept hex). You can then later disable by changing that back to 0.

You do not provide enough information. What version of FSUIPC? What version of prepar3d? Did you register your key during the installation process? Please attach your .log file.

Thanks Paul. I'll add them to the SDK for the next release - you can zip them up and attach them when ready.

Hi Julius, I'm sorry but I cannot understand what you are trying to say. Can you please answer the following questions: Is this problem for the PMDG aircraft only? Do the brakes work for all or any other aircraft (you said it was working in the FS-Labs-320, no)? Why do you say "RightBrake good" for the PMDG? If this is the case, then you do not have a problem. IF your problem is only with PMDG, then you could try with sending the brake axis to the FS rather than to FSUIPC calibration (and remove the calibration entry). However, if you do this, you may need to add the scaling I previously provided otherwise your range would be too small (0-1023), and may also need to reverse (by making the multiplier negative and adding 16384 rather than subtracting), But before you try anything else, I really need to see your .ini (the whole file, not extracts), and the log file with Axis controls logging active, and showing each brake activated separately through its full range. I have asked for this several times now, and cannot help further if you do not provide these. Cheers, John

Hi Patrick, this sounds like it would be interesting (I was a java developer for 20+ years), but unfortunately I have no time at all to look into this at the moment or for the foreseeable future. I will make a note though to take a look at some point, but I can't see this happening until much later in the year. Regards, John

If your right brake is good, do the same for the left brake then. But if that is the case, what is your problem?

Hi, could you please try the following dll: FSUIPC5.DLL I've tested with your script and the release is printed with the shift. Cheers, John

Hi Eran, ok, not sure what you mean but I'm glad your problem is resolved! John