johnliem Posted July 2, 2017 Report Posted July 2, 2017 Hello Pete I use FSUIPC5 for a couple weeks, suddenly FSUIPC5 does not detect my joystick and all the buttons, the only FSUIPC5 detect is my rudder which I use the axes assignment, I use joystick Hotas Warthog and the rudder, yoke and Rudder from Saitek, what I have done so far, I delete the file under module and reinstall it, but still when I start P3D Version 4 I can only use the Rudder and no buttons , can you tell me what I have done wrong ? thanks
Thomas Richter Posted July 2, 2017 Report Posted July 2, 2017 Hi, please copy and paste the following files after a short session and a fully closed FS (P3D), FSUIPC5.ini / FSUIPC5.log / FSUIPC5.JoyScan.csv Thomas
johnliem Posted July 2, 2017 Author Report Posted July 2, 2017 Thanks for quick respons Thomas, FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log
Thomas Richter Posted July 2, 2017 Report Posted July 2, 2017 Hi, for some reason those devices have the same GUID and ID, where they are unique in Windows (should be). 156 Device acquired for use: 156 Joystick ID = 3 (Registry okay) 156 3=Saitek Pro Flight Quadrant 156 3.GUID={4667AD50-4C6F-11E7-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 3 (Registry okay) 156 3=Joystick - HOTAS Warthog 156 3.GUID={4667AD50-4C6F-11E7-8001-444553540000} Can you please download and run the HidScanner (from Useful additional programs) and send as well its log file. Thomas
johnliem Posted July 2, 2017 Author Report Posted July 2, 2017 Hi here is the log file you asked me to send. HidScanner.log
johnliem Posted July 2, 2017 Author Report Posted July 2, 2017 Hi Thomas, I figure it out, why this happend it seem that my extra keypad Orbeaver chroma cause this issue, well the solution is just unplugged the Orbeaver chroma first before I start the P3D and then plug in, well for the time being I am quite happy to do this action, but my question is, is there a solution to fix this problem? FYI this Orbeaver chroma cause also P3D Version 4 to start, but after the last hotfix, the issue is solved , and I can start P3D with Orbeaver chroma connnected, this the text from P3D Fixed a crash on startup due to controllers using bad port and hub values thanks for your support so far. see the log file which 109 Product= <not readable at this time: maybe device disconnected?> 109 Vendor=1532, Product=0207 (Version 1.1) 109 GUIDs returned for product: VID_1532&PID_0207: 109 GUID= {04F83160-3954-11E7-800E-444553540000} 109 Details: Btns=3, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 109 GUID= {04F683B0-3954-11E7-800C-444553540000} 109 Details: Btns=573, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 109 GUID= {04F9B800-3954-11E7-8011-444553540000} 109 Details: Btns=24, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255 FSUIPC5.log
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