Hello:
I have a USB PFC Cirrus 2 Pro console which used to work properly with MSFS using the Beta version of FSUIPC 7, PFChid64, and Thomas’ suggested additions to PFChid64.ini.
With my newly registered version of FSUIPC7, the Cirrus 2 Pro no longer works - none of the axes (Elevator, Aileron, Throttle, Mixture, Prop) are detected by the FSUIPC7 “Axes Assignments” section on the “Axis Assignments and Calibration” tab. Interestingly, my separate set of PFC Cirrus USB Rudder pedals are immediately detected by FSUIPC7.
The FSUIPC7.log file indicates that PFDhid64.dll is loading ok and that the PFC devices are identified.
I can no longer find the PFChid64.ini and the PFChid64.log files.
All axes and switches of the Cirrus 2 Pro work properly when tested with the PFCTestGUI utility.
Does anyone have any suggestions for further troubleshooting ?
Thanks very much -
Jack
***********
Addendum: It's now mostly working:
I tried disconnecting and reconnecting the USB from the Cirrus 2 Pro.
FSUIPC7 can now detect the axes of the Throttle/Prop/Mixture controls.
Although the Elevator and Aileron axes of the C2 appear to be undetected by FSUIPC7, they are actually being passed to MSFS along with all the other switches on the console. This is a different behavior than that of the FSUIPC7 Beta which did allow detection and setting of calibration curves for both the Elevator and Aileron.
This can partially be worked around by use of the PFC calibration utility.
Jack
FSUIPC7.ini FSUIPC7.log
