Braudoux Posted March 1 Report Posted March 1 Hello, My controller AXAIR is no longer recognized by FSUIPC, whatever USB I use on the computer. While checking the FSUIPC6.ini file, I noticed that there are twice the same reference and I suspect that it is the origin of the problem. Could you confirm? [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={E94396F0-E721-11EB-8004-444553540000} E=Saitek Pro Flight X-55 Rhino Stick E.GUID={E942D3A0-E721-11EB-8002-444553540000} B=MIAP STD B.GUID={4981D2D0-E40F-11EC-8001-444553540000} C=MIAP STD C.GUID={E942D3A0-E721-11EB-8002-444553540000} D=Saitek Pro Flight X-55 Rhino Stick D.GUID={E9436FE0-E721-11EB-8003-444553540000} Thanks in advance Regards Bruno
John Dowson Posted March 1 Report Posted March 1 6 hours ago, Braudoux said: While checking the FSUIPC6.ini file, I noticed that there are twice the same reference and I suspect that it is the origin of the problem. Could you confirm? [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={E94396F0-E721-11EB-8004-444553540000} E=Saitek Pro Flight X-55 Rhino Stick E.GUID={E942D3A0-E721-11EB-8002-444553540000} B=MIAP STD B.GUID={4981D2D0-E40F-11EC-8001-444553540000} C=MIAP STD C.GUID={E942D3A0-E721-11EB-8002-444553540000} D=Saitek Pro Flight X-55 Rhino Stick D.GUID={E9436FE0-E721-11EB-8003-444553540000} So it looks like the GUIDs have changed, not only for that device but also for your Saitek Pro Flight X-55 Rhino Stick, which now has two device letters D and E. If the GUID if your MIAP STD is now that in the C entry, but your assignments are referencing B, then switch the GUIDs and remove the C entry, ie. Quote JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={E94396F0-E721-11EB-8004-444553540000} E=Saitek Pro Flight X-55 Rhino Stick E.GUID={E942D3A0-E721-11EB-8002-444553540000} B=MIAP STD B.GUID={E942D3A0-E721-11EB-8002-444553540000} D=Saitek Pro Flight X-55 Rhino Stick D.GUID={E9436FE0-E721-11EB-8003-444553540000} You should also do similar for your Saitek Pro Flight X-55 Rhino Stick. Also, please attach the full ini file next time rather than posting extracts, and also attach your FSUIPC7.log file for any further issues. John
Braudoux Posted March 2 Author Report Posted March 2 Thanks John. After modifying the ini file as per your suggestion, I am facing now a new issue: FSUIPC doesn't start (FSUIPC not availale in Add-ons menu in P3D). I might have done something wrong, for sure. I attach the FSUIPC6-copy.ini file which is the original file before modification, the FSUIPC6.ini file after modification and the FSUIPC6.log. Please note that the later was not modified since the program did not start, so it is the latest log file before I touch anything, I'd like to add that, for testing purpose, I have deleted the FSUIPC6.ini file and restarted P3D. expecting that a new .ini file would be created but nothing happened. Thanks again for your help Regards Bruno FSUIPC6 - Copy.ini FSUIPC6.ini FSUIPC6.log
John Dowson Posted March 4 Report Posted March 4 On 3/2/2025 at 9:06 AM, Braudoux said: I'd like to add that, for testing purpose, I have deleted the FSUIPC6.ini file and restarted P3D. expecting that a new .ini file would be created but nothing happened. Well, it cannot create the ini file if it isn't running. P3D starts FSUIPC from either the DLL.xml file or the Documents\Prepar3d v? Add-ons\FSUIPC6\add-on.xml file (depending on P3D version and maybe the components selected during installation), which are either modified or created when you install and has absolutely nothing at all to do with your ini file. Check you InstallFSUIPC6.log file for details. Changing the ini file can in no way affect the starting of FSUIPC6, so you must have also done something else. You can always try re-installing FSUIPC6 to see if that helps, and if not then show me / attach your InstallFSUIPC6.log file. John
Braudoux Posted March 4 Author Report Posted March 4 Hello John, I reinstalled FSUIPC and it solved the problem of starting with P3D. So now I need to resolve the duplicates in the Joysticks Names. In order to test my MIAP controller with FSUIPC, I shut down P3D and deleted the FSUIPC.ini file. After relaunching P3D, I opened the new FSUIPC file and noticed that the controller is not detected (not listed). The same controller is detected by P3D itself and is reacting to the presets. Is it possible that the bindings set in P3D are preventing FSUIPC to detect the MIAP controller? Find attached the required files. FSUIPC6 (after reinstal).ini FSUIPC6 (after deletion).ini FSUIPC6.log
John Dowson Posted March 4 Report Posted March 4 8 minutes ago, Braudoux said: In order to test my MIAP controller with FSUIPC, I shut down P3D and deleted the FSUIPC.ini file. But why? Why not just do the correction I suggested? 9 minutes ago, Braudoux said: After relaunching P3D, I opened the new FSUIPC file and noticed that the controller is not detected (not listed). It was detected: Quote 672 ---------------------- Joystick Device Scan ----------------------- 687 Product= Saitek Pro Flight X-55 Rhino Stick 687 Manufacturer= Madcatz 687 Serial Number= G0001739 687 Vendor=0738, Product=2215 (Version 0.87) 687 GUIDs returned for product: VID_0738&PID_2215: 687 GUID= {E942D3A0-E721-11EB-8002-444553540000} 687 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0 687 GUID= {E9423760-E721-11EB-8001-444553540000} 687 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 687 Product= MIAP STD 687 Manufacturer= AXAIR 687 Serial Number= HIDDC 687 Vendor=2354, Product=8049 (Version 1.0) 687 GUIDs returned for product: VID_2354&PID_8049: 687 GUID= {4981D2D0-E40F-11EC-8001-444553540000} 687 Details: Btns=38, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 687 Product= Saitek Pro Flight X-55 Rhino Throttle 687 Manufacturer= Madcatz 687 Serial Number= PP000503 687 Vendor=0738, Product=A215 (Version 0.119) 687 ------------------------------------------------------------------- However, it was not acquired as you now have registry issues: Quote 703 WARNING: Joystick ID 0 is duplicated in Registry 703 WARNING: Joystick ID 1 is duplicated in Registry 703 Device acquired for use: 703 Joystick ID = 0 (Registry okay) 703 0=Saitek Pro Flight X-55 Rhino Stick 703 0.GUID={E942D3A0-E721-11EB-8002-444553540000} 703 Device acquired for use: 703 Joystick ID = 1 (Registry okay) 703 1=MIAP STD 703 1.GUID={E94396F0-E721-11EB-8004-444553540000} 703 Device acquired for use: 703 Joystick ID = 0 (Registry okay) 703 0=Saitek Pro Flight X-55 Rhino Throttle 703 0.GUID={E942D3A0-E721-11EB-8002-444553540000} 703 Device acquired for use: 703 Joystick ID = 1 (Registry okay) 703 1=Saitek Pro Flight X-55 Rhino Throttle 703 1.GUID={E94396F0-E721-11EB-8004-444553540000} 703 ------------------------------------------------------------------- Continually unplugging and changing USB ports can cause registry issues. Please go back to your previous ini, make the changes I suggested and try again. If you still get issues, please attach your log and ini files again please, as well as the JoyScan.csv file. 14 minutes ago, Braudoux said: Is it possible that the bindings set in P3D are preventing FSUIPC to detect the MIAP controller? No, it is due to registry issues. If assi9gning in FSUIPC, we recommend that you disable controllers completely in P3D. If you don't do this, please make sure that you don't have dual assignments, i.e. an axis or button/switch assigned in both FSUIPC and P3D. Also, P3D has a tendency to auto-detect your controllers (if not disabled) and then make default assignments, which can cause issues if already assigned in FSUIPC. John
Braudoux Posted March 6 Author Report Posted March 6 Dear John I have proceeded to the correction as per your advice. This is what I have set in the para [JoyNames] [JoyNames] AutoAssignLetters=Yes A=SAITEK PRO FLIGHT X-55 RHINO THROTTLE A.GUID={E94396F0-E721-11EB-8004-444553540000} B=MIAP STD << MISSING JOYSTICK >> B.GUID={4981D2D0-E40F-11EC-8001-444553540000} F=Saitek Pro Flight X-55 Rhino Throttle F.GUID={E942D3A0-E721-11EB-8002-444553540000} All assignments attached to F correspond to the joystick in fact. After launching P3D, my MIAP controller is still not detected, as specified earlier, despite it is detected by P3D itself. In the new FSUIPC.ini (attached): the system created [1] and [0], generating new duplicates again. a message shows that [E] is missing. [B] is declared MISSING I did not unplug any device. When I go to the configuration tool, any button I click on my MIAP are not detected. So I don't know what to do 😞 Regards FSUIPC6.log FSUIPC6.ini FSUIPC6.JoyScan.csv
John Dowson Posted March 6 Report Posted March 6 This is very strange: Quote ,,, HIDscanning completed N, x00, x0738, x2215, , -1, -1, 0, {NULL}, {NULL}, {E942D3A0-E721-11EB-8002-444553540000}, Y, N N, x00, x0738, x2215, , -1, -1, 0, {NULL}, {NULL}, {E9423760-E721-11EB-8001-444553540000}, N, N N, x00, x2354, x8049, , -1, -1, 0, {NULL}, {NULL}, {4981D2D0-E40F-11EC-8001-444553540000}, Y, N N, x00, x0738, xA215, , -1, -1, 0, {NULL}, {NULL}, {E942D3A0-E721-11EB-8002-444553540000}, Y, N i.e. you have two different devices (x2215 and xA215) from the same vendor (x0738) that have the same GUID (E942D3A0-E721-11EB-8002-444553540000). GUIDs are allocated by windows and should be unique... Do you have any additional software or drivers installed for your devices? If so, please uninstall and delete any specific drivers, especially any Saitek drivers, and let windows install its default drivers. And do not use any additional saitek software when using FSUIPC. Also, please do the following: 1. Take a backup of your registry, using the windows Registry Editor 2. Unplug all your devices 3. Download and run (i.e. double-click) the following regedit script: removeDevices.reg This will remove the current registry entries for your devices 4. Reboot your PC 5. Reconnect your devices 6. Run P3d and FSUIPC - just start it, load an aircraft and then exit 7. Show me / attach those 3 files again. Do not make any further changes at the moment John
John Dowson Posted March 6 Report Posted March 6 By the way, I have the X-55s and this is how mine are detected in the log: Quote 641 Product= Saitek Pro Flight X-55 Rhino Throttle 641 Manufacturer= Madcatz 641 Serial Number= G0001630 641 Vendor=0738, Product=A215 (Version 0.119) 641 GUIDs returned for product: VID_0738&PID_A215: 641 GUID= {8B238AC0-45DE-11EA-800C-444553540000} 641 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255 641 Product= Saitek Pro Flight X-55 Rhino Stick 641 Manufacturer= Madcatz 641 Serial Number= G0003298 656 Vendor=0738, Product=2215 (Version 0.87) 656 GUIDs returned for product: VID_0738&PID_2215: 656 GUID= {8B23B1D0-45DE-11EA-800E-444553540000} 656 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 i.e. each one detected with a single GUID. Your log shows the stick with 2 GUIDs and no GUID for the throttle: Quote 687 ---------------------- Joystick Device Scan ----------------------- 687 Product= Saitek Pro Flight X-55 Rhino Stick 687 Manufacturer= Madcatz 687 Serial Number= G0001739 687 Vendor=0738, Product=2215 (Version 0.87) 765 GUIDs returned for product: VID_0738&PID_2215: 765 GUID= {E942D3A0-E721-11EB-8002-444553540000} 765 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0 765 GUID= {E9423760-E721-11EB-8001-444553540000} 765 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 .... 781 Product= Saitek Pro Flight X-55 Rhino Throttle 781 Manufacturer= Madcatz 781 Serial Number= PP000503 781 Vendor=0738, Product=A215 (Version 0.119) 781 ------------------------------------------------------------------- This is usually due to having installed saitek drivers and maybe additional software, so please remove those (or don't run any additional saitek software when using FSUIPC).
Braudoux Posted March 7 Author Report Posted March 7 15 hours ago, John Dowson said: Do you have any additional software or drivers installed for your devices? If so, please uninstall and delete any specific drivers, especially any Saitek drivers, and let windows install its default drivers. And do not use any additional saitek software when using FSUIPC. Hello. Nope, I have no other software than FSUIPC... Then I have followed the checklist above: run the removeDevices software, Restarted my computer Launched P3D and loaded a scenario with C130 Exited the simulator. Here are the 3 files FSUIPC6.log FSUIPC6.ini FSUIPC6.JoyScan.csv
John Dowson Posted Friday at 12:18 PM Report Posted Friday at 12:18 PM (edited) 5 hours ago, Braudoux said: Hello. Nope, I have no other software than FSUIPC... Ok. Those files look food now. Please use/try the attached FSUIPC6.ini and you should be ok. Any issues, please show me the files again. It also seems that the GUIDs of your devices have changed a few times (probably due to windows updates), and when this has happened you have re-assigned. If this happens again, you should correct the [JoyNames] section so that the assigned letters are using the new GUIDs and not re-assign to the new letters. Or post your files here the next time and I can show you what you need to do when this happens. John FSUIPC6.ini P.S. You are using version 6.2.1 - the latest and only supported version is 6.2.2. There are only minor changes in this version, but please update at your convenience. Edited Friday at 01:59 PM by John Dowson Added recommendation to update
Braudoux Posted Saturday at 03:47 AM Author Report Posted Saturday at 03:47 AM 15 hours ago, John Dowson said: it also seems that the GUIDs of your devices have changed a few times (probably due to windows updates), and when this has happened you have re-assigned. If this happens again, you should correct the [JoyNames] section so that the assigned letters are using the new GUIDs and not re-assign to the new letters. Or post your files here the next time and I can show you what you need to do when this happens Hello John, All good now, thanks you very much. This experience made me understand better the structure of the INI file. Still not quite sure controllers are repeated 3 times in the [JoyNames] section... For example the MIAP is referenced as A, 1 and D. The same goes for the other 2 controllers... Anyway that works and I will upgrade to 6.2.2 version. Best regards and thanks again Bruno
John Dowson Posted Saturday at 11:41 AM Report Posted Saturday at 11:41 AM 7 hours ago, Braudoux said: Still not quite sure controllers are repeated 3 times in the [JoyNames] section... For example the MIAP is referenced as A, 1 and D. The same goes for the other 2 controllers... Sorry, I left those in by mistake... This is your [JoyNames] section - please delete the entries in bold: Quote [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Throttle A.GUID={B45E0690-FB6E-11EF-8005-444553540000} B=MIAP STD B.GUID={B45DDF80-FB6E-11EF-8003-444553540000} C=Saitek Pro Flight X-55 Rhino Stick C.GUID={B45DB870-FB6E-11EF-8002-444553540000} 0=Saitek Pro Flight X-55 Rhino Stick 0.GUID={B45DB870-FB6E-11EF-8002-444553540000} 1=MIAP STD 1.GUID={B45DDF80-FB6E-11EF-8003-444553540000} 2=Saitek Pro Flight X-55 Rhino Throttle 2.GUID={B45E0690-FB6E-11EF-8005-444553540000} D=MIAP STD --? B D.GUID={B45DDF80-FB6E-11EF-8003-444553540000} G=Saitek Pro Flight X-55 Rhino Throttle --> A G.GUID={B45E0690-FB6E-11EF-8005-444553540000} F=Saitek Pro Flight X-55 Rhino Throttle << MISSING JOYSTICK >> --> A E=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> Every device should have 4 entries - a name and GUID entry with a number, and a name and GUID entry with a letter.
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