AZWildk4t Posted December 11, 2019 Report Posted December 11, 2019 Hi Pete. I received my PFC Jetliner Yoke last week and trying to use FSUIPC to set it up. I added the PFC.dll and PFCcom64.dll to the modules folder like the instructions state. However, I am unclear which COM port to use since it's USB. When I select any of the COM ports using PFC Control Connections Check, it puts a green checkmark next to the COM port connect but the 2 Yoke checks fail. Can you tell me what I am doing incorrectly in the setup? Do I need to use PFC DLLs if it's a USB connection? Thanks, Steve
Thomas Richter Posted December 11, 2019 Report Posted December 11, 2019 Hi, Quote PFC.dll also needs FSUIPC Version 3.70 or later for correct operation. The current version is 3.999PFCFSX.dll needs FSUIPC4 for FSX/P3D—any version, but latest is best. The current version is 4.968PFCcom64.dll needs FSUIPC5 for P3D4—any version from 5.101 onwards, but latest is best. Quote PFChid.dll The PFChid module for 32-bit simsPFChid64.dll The PFChid module for 64-bit sims So as you can see and as the manual states you will need for a USB version the PFChid version of the driver. Depending on which FS you use only one of the both but not both. If you use FSUIPC4 then it is PFChid.dll and if you use FSUIPC5 (P3Dv4) then you need PFChid64.dll. But again only one of the both, remove any other PFC dll you already installed! Thomas
AZWildk4t Posted December 12, 2019 Author Report Posted December 12, 2019 10 hours ago, Thomas Richter said: So as you can see and as the manual states you will need for a USB version the PFChid version of the driver. Depending on which FS you use only one of the both but not both. If you use FSUIPC4 then it is PFChid.dll and if you use FSUIPC5 (P3Dv4) then you need PFChid64.dll. Thanks Thomas. I was looking at the PFC.dll documentation instead of the FSUIPC5 documentation. Is FSUIPC6 a typo? I only have FSUIPC5. [Was a typo, now corrected to avoid misleading other readers]
Thomas Richter Posted December 12, 2019 Report Posted December 12, 2019 Hi, it's FSUIPC5 (P3Dv4). The latest download from Jun 2017 is correct. I must have copied from an older PDF. (download link below) PFC HID device driver for FS9, FSX, FSX-SE and P3D PFCHIDincludes PFChid.DLL for 32-bit sims, and PFChid64.dll for P3D4. Thomas
Pete Dowson Posted December 12, 2019 Report Posted December 12, 2019 12 hours ago, AZWildk4t said: I received my PFC Jetliner Yoke last week and trying to use FSUIPC to set it up. I added the PFC.dll and PFCcom64.dll As Thomas says, it's EITHER PFC.DLL (32-bit) OR PFCcom64.DLL (64-bit) for a serial port PFC device, depending on which Flight Sim and FSUIPC you are using. However, if this is a new PFC yoke then surely it is a normal USB devce, looking like a Joystick to Windows? The older PFC products were serial port based and using one of those two drivers I produced, but I thought all of their recent stuff was more universal? The PFCHid.DLL and PFChid64.DLL drivers were made for non-joystick type PFC USB products which adhere to the Windows "Human Interface Device" standards (hence 'HID'), such as the Cirrus consoles. Pete
brianVancouver Posted August 13, 2020 Report Posted August 13, 2020 Hello, I am wanting to install a pfc jetliner usb yoke, using a purchased version of FSUIPC v 6 in PSD 4,5. FSUIPC is present, but the yoke is not listed. Using Windows (10), the yoke is identified in the devices page, but states that the driver is missing. I am not terribly computer savvy, so need step by step instructions in order to know how to effect the installation. Is this something you can provide? Best regards, Brian
Pete Dowson Posted August 13, 2020 Report Posted August 13, 2020 3 hours ago, brianVancouver said: I am wanting to install a pfc jetliner usb yoke, using a purchased version of FSUIPC v 6 in PSD 4,5. FSUIPC is present, but the yoke is not listed. Using Windows (10), the yoke is identified in the devices page, but states that the driver is missing. I'm pretty sure that the USB yoke they make is a standard joystick device and doesn't need FSUIPC. It should be recognised by Windows Game Controllers as a normal joystick and by P3D. If Windows doesn't see it then FSUIPC cannot either. But you're saying that Windows complains that it needs a driver? In Windows Device manager is it listed as a COM device or only a USB device? And how listed in Windows Settings? By name? Pete
brianVancouver Posted August 13, 2020 Report Posted August 13, 2020 First -- Thank you for getting back to me. I know you're very busy. When I look in "game controllers", it does not appear. In Windows Settings, it appears as: PFC USB Yoke (Driver Error). Finally, when I check via "Control Panel' -- "hardware and sound" -- "devices and printers": it appears as "PFC USB Yoke" (with an amber asterisk -- saying "usb input device has a driver problem". Finally, it says "Problem with PnP devices (detected). There are problems with some PnP devices. Windows will take additional steps to further troubleshoot these devices". Troubleshooting doesn't have an effect. Hopefully, some of this makes sense to you? Best regards, Brian
brianVancouver Posted August 13, 2020 Report Posted August 13, 2020 Hello Pete, Problem resolved. I found I was able to install the driver from my pc using the Game Controllers. It seems to be working properly. Thank you for your advice, Best regards, Brian
brianVancouver Posted August 13, 2020 Report Posted August 13, 2020 An added problem was that I had installed the PFC yoke and rudder pedals in USB 3,0 ports, which seemed to cause them to crash. They're now installed in 2,0 ports and appear to be stable. Again, thank you for taking the time to help, Best regards, Brian
Pete Dowson Posted August 14, 2020 Report Posted August 14, 2020 7 hours ago, brianVancouver said: Problem resolved. Good. 7 hours ago, brianVancouver said: An added problem was that I had installed the PFC yoke and rudder pedals in USB 3,0 ports, which seemed to cause them to crash. They're now installed in 2,0 ports and appear to be stable. Yes, that seems to be a common problem. You wouldn't have thought that in developing a faster interface they'd lose some compatibility with the previous incarnation. Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now