Danny81 Posted April 15, 2017 Report Share Posted April 15, 2017 Hi I'm running the latest latest p3d v3 version and the new fsuipc 4.966 both fresh installs as well as windows 10 pro the problem I have is that one of the TQ is not recognised in fsuipc it works in the control setup in P3D and in devices and printers. I have made sure they both work by using one at a time and they work fine in fsuipc, but then I plug both in at the same time again only one works. I have tried changing the joystick id using joyid and that doesn't seem to work. This has recently just started to happen they did work before perfectly well. Im getting frustrated I tried everything Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 15, 2017 Report Share Posted April 15, 2017 23 minutes ago, Danny81 said: the problem I have is that one of the TQ is not recognised in fsuipc it works in the control setup in P3D and in devices and printers. I have made sure they both work by using one at a time and they work fine in fsuipc, but then I plug both in at the same time again only one works. I have tried changing the joystick id using joyid and that doesn't seem to work. This has recently just started to happen they did work before perfectly well. What changed? P3D or FSUIPC or both? Or Windows, what, the really good Win7 to the problematic Win10? No need to use JoyID these days. FSUIPC does what that used to be needed for, to make sure proper IDs were assigned. I'd need more details, like your FSUIPC4.INI and a LOG. You can paste their contents here. Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 15, 2017 Author Report Share Posted April 15, 2017 hope this helps nothing changes just done a clean install of windows 10 and P3d the fsuipc is the newest one FSUIPC4.log FSUIPC4.ini Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2017 Report Share Posted April 16, 2017 8 hours ago, Danny81 said: hope this helps nothing changes just done a clean install of windows 10 and P3d the fsuipc is the newest one Nothing changed? Installing Windows is a huge change and almost always changes all the GUID and Joystick IDs! For some reason Microsoft has registered your Saitek Pro Flight Quadrant twice with EXECTLY the same GUID! 19000 ---------------------- Joystick Device Scan ----------------------- 19000 Product= Saitek Pro Flight Quadrant 19000 Manufacturer= Saitek 19000 Vendor=06A3, Product=0C2D (Version 2.2) 19000 Assigned joystick id 2 (fixed Registry) 19000 GUID= {71690BD0-222A-11E7-8002-444553540000} 19000 Product= T-Rudder 19000 Manufacturer= Thrustmaster 19000 Vendor=044F, Product=B679 (Version 1.16) 19000 Assigned joystick id 0 (Registry okay) 19016 GUID= {A17BFC30-221E-11E7-8009-444553540000} 19031 Product= Saitek Pro Flight Quadrant 19031 Manufacturer= Saitek 19031 Vendor=06A3, Product=0C2D (Version 2.2) 19031 Assigned joystick id 3 (fixed Registry) 19031 GUID= {71690BD0-222A-11E7-8002-444553540000} 19031 Product= Saitek Pro Flight X-55 Rhino Stick 19031 Manufacturer= Madcatz 19031 Serial Number= G0000016 19031 Vendor=0738, Product=2215 (Version 0.87) 19031 Assigned joystick id 1 (Registry okay) 19031 GUID= {A1DEAA10-2228-11E7-8001-444553540000} 19031 ------------------------------------------------------------------- and it looks like the T-Rudder joined the party late (see the two separate joystick scans because of that). If you have two throttle quadrants they MUST have different GUIDs, otherwise FSUIPC will only be able to access one of them -- and the Joystick ID might keep changing. I am suspecting something odd in your registry. Please run Regedit (from the place Win10 allows you to type in program names to look for them). You will see it comes up with an Explorer type Window. Navigate right down to HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput then, in the File Menu select Export ... and choose a place to save the data -- save it as a Txt file, NOT a Reg or you won't be able to upload it here. then, before leaving Regedit, do the same (but with a different name of course) with HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput (Don't worry if you can't find one of the above. As long as one of them is there. But there are both normally). Then please show me both files. I am rather worried that the new Joystick scanning mechanism I implemented, which was supposed to solve these sorts of problems properly, may not cover all cases after all. I should be able to tell from this data whether it is me or you genuinely do have a Registry problem. Thanks, Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 Hi the only one in my REG was HKEY_CURRENT_USER nothing in the other one Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:25 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_B679 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_B679\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_B679\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:46 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 09 44 45 53 54 00 00 0ü{¡."ç.. DEST.. Value 1 Name: Joystick Id Type: REG_BINARY Data: 00000000 00 00 00 00 .... Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_B679\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_B679\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:12 PM Value 0 Name: 7&6D2E5E3&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 7&3687AB09&0&0000 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 05 44 45 53 54 00 00 0ü{¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\1 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 08 44 45 53 54 00 00 0ü{¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\1\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\2 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 6d 7e a1 1e 22 e7 11 - 80 0a 44 45 53 54 00 00 0m~¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\Calibration\2\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C07C\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: 8&975D51D&0&0001 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 8&975D51D&0&0002 Type: REG_BINARY Data: 00000000 02 . Value 2 Name: 8&975D51D&0&0003 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 06 44 45 53 54 00 00 0ü{¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\Calibration\1 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 07 44 45 53 54 00 00 0ü{¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\Calibration\1\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C22D\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: 7&27644400&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 7&27644400&0&0001 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 40 b2 79 a1 1e 22 e7 11 - 80 01 44 45 53 54 00 00 @²y¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\1 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 40 b2 79 a1 1e 22 e7 11 - 80 02 44 45 53 54 00 00 @²y¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\1\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\2 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 40 b2 79 a1 1e 22 e7 11 - 80 03 44 45 53 54 00 00 @²y¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\2\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\3 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 fc 7b a1 1e 22 e7 11 - 80 04 44 45 53 54 00 00 0ü{¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\Calibration\3\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C531\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: 8&3A0A5E94&0&0001 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 8&3A0A5E94&0&0002 Type: REG_BINARY Data: 00000000 02 . Value 2 Name: 8&3A0A5E94&0&0003 Type: REG_BINARY Data: 00000000 02 . Value 3 Name: 8&3A0A5E94&0&0004 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:25 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:25 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 11:35 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 d0 0b 69 71 2a 22 e7 11 - 80 02 44 45 53 54 00 00 Ð.iq*"ç...DEST.. Value 1 Name: Joystick Id Type: REG_BINARY Data: 00000000 03 00 00 00 .... Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:25 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 11:35 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 80 48 68 71 2a 22 e7 11 - 80 01 44 45 53 54 00 00 .Hhq*"ç...DEST.. Value 1 Name: Joystick Id Type: REG_BINARY Data: 00000000 02 00 00 00 .... Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:25 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:50 PM Value 0 Name: 6&806233C&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 6&30E73C9E&1&0000 Type: REG_BINARY Data: 00000000 02 . Value 2 Name: 6&806233C&1&0000 Type: REG_BINARY Data: 00000000 02 . Value 3 Name: 6&30E73C9E&2&0000 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0D67 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0D67\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0D67\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 30 6d 7e a1 1e 22 e7 11 - 80 0d 44 45 53 54 00 00 0m~¡."ç...DEST.. Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0D67\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 9:01 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0D67\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 11:34 PM Value 0 Name: 6&1475848&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 6&1475848&1&0000 Type: REG_BINARY Data: 00000000 02 . Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:12 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:12 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:46 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 10 aa de a1 28 22 e7 11 - 80 01 44 45 53 54 00 00 .ªÞ¡("ç...DEST.. Value 1 Name: Joystick Id Type: REG_BINARY Data: 00000000 01 00 00 00 .... Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0\Type Class Name: <NO CLASS> Last Write Time: 4/16/2017 - 12:39 AM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0\Type\Axes Class Name: <NO CLASS> Last Write Time: 4/16/2017 - 12:39 AM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0\Type\Axes\0 Class Name: <NO CLASS> Last Write Time: 4/16/2017 - 12:39 AM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0\Type\Axes\1 Class Name: <NO CLASS> Last Write Time: 4/16/2017 - 12:39 AM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\0\Type\Axes\5 Class Name: <NO CLASS> Last Write Time: 4/16/2017 - 12:39 AM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\1 Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:12 PM Value 0 Name: GUID Type: REG_BINARY Data: 00000000 00 f4 e0 a1 28 22 e7 11 - 80 02 44 45 53 54 00 00 .ôà¡("ç...DEST.. Value 1 Name: Joystick Id Type: REG_BINARY Data: 00000000 03 00 00 00 .... Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\Calibration\1\Type Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 10:12 PM Key Name: HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2215\DeviceInstances Class Name: <NO CLASS> Last Write Time: 4/15/2017 - 11:34 PM Value 0 Name: 7&21320576&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 1 Name: 7&2D45B6F3&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 2 Name: 7&117A3A4F&0&0000 Type: REG_BINARY Data: 00000000 02 . Value 3 Name: 7&1D8DEBCC&0&0000 Type: REG_BINARY Data: 00000000 02 . Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2017 Report Share Posted April 16, 2017 17 minutes ago, Danny81 said: Hi the only one in my REG was HKEY_CURRENT_USER nothing in the other one That's fine. The registry definitely has different GUIDs for each device, so it must be something daft my code is doing. I'm trying to emulate having two quadrants here by fiddling the registry but it won't work. It has to see them too. I'll let you know as soon as I've got to the bottom of it. The odd thing is that since 4.966 was released only yesterday I've already had two similar reports, although this code has not changed at all in 4.966 -- it was like this in 4.965 two weeks ago! Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 well i was using the 4.965 and things seem to work ok no problems when i first got the TQ's then after a fresh install of P3D and FSUIPC 4.965 the problem started same with 4.966. well good luck i cant seem to figure out what went wrong. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2017 Report Share Posted April 16, 2017 Further to my last reply, to help me work out what is wrong could you please add these lines to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x200000 then run the Sim (only till ready to fly, then close) and show me the FSUIPC4.LOG. You can remove those two lines afterwards. Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 Quote YEP NO PROBLEMS Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 to clarify you like me just to load in to the the start up menu or load in to a airport with aircraft FSUIPC4.log Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 just to let you Know i did a experiment i had a older fsuipc 4.955c and would you believe it it sort my problem out i now have both throttle working so here are the files for it thought it might help. FSUIPC4.log fsuipc4.ini Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2017 Report Share Posted April 16, 2017 Just now, Danny81 said: i did a experiment i had a older fsuipc 4.955c and would you believe it it sort my problem out Sorry, I know! The change to joystick handling, to deal with the numerous cases of missing joystick IDs and FSUIPC not seeing many joysticks, was first implemented in 4.964. It worked beautifully in Windows 7, using some Windows functions just made for the job! But then it was found that these functions crashed FS in Windows 10. They are broken. I don't know when MS will fix them, but I cannot wait. So I looked for an alternative and worked out one which was implemented in 4.965 a couple of weeks ago (and some pre-releases before that). It all appeared to be working and I received few if any problems with it. Now, just one day after releasing 4.966, with NO CHANGES in this, I get 4 reports of these problems all on the same day! Weird, and not a little frustrating! I am working hard to try to fix it. At least I can now reproduce it, having found two spare Bodnar boards and connected them (with no switch or stick connections) to the test PC. Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 16, 2017 Author Report Share Posted April 16, 2017 good luck Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2017 Report Share Posted April 16, 2017 Please try FSUIPC 4.966b and let me know. Just open the ZIP and copy over the FSUIPC4.DLL into your Modules folder. It is working fine here with multiple Bodnar boards (all i could find here today). Pete Link to comment Share on other sites More sharing options...
Danny81 Posted April 17, 2017 Author Report Share Posted April 17, 2017 no worries i will try first thing in the morning and get back to you in a 9hr long haul got 4hrs left till landing Link to comment Share on other sites More sharing options...
ASadik Posted April 17, 2017 Report Share Posted April 17, 2017 8 hours ago, Pete Dowson said: Please try FSUIPC 4.966b and let me know. Just open the ZIP and copy over the FSUIPC4.DLL into your Modules folder. It is working fine here with multiple Bodnar boards (all i could find here today). Pete Hi Pete, Same issue with me. But this B update didn't seem to do the trick. Link to comment Share on other sites More sharing options...
ASadik Posted April 17, 2017 Report Share Posted April 17, 2017 19 minutes ago, ASadik said: Hi Pete, Same issue with me. But this B update didn't seem to do the trick. Also I just installed 4955c and that worked fine as well, so for the moment that's what I'm running. Link to comment Share on other sites More sharing options...
Danny81 Posted April 17, 2017 Author Report Share Posted April 17, 2017 well i tested 4.966b just now and works no problems so far added my log and ini file for you to see results both throttle work well do a extensive test later FSUIPC4.log FSUIPC4.ini Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 17, 2017 Report Share Posted April 17, 2017 Hi, both throttle have now their correct unique GUID, so that will work correct in any case. Thomas Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 17, 2017 Report Share Posted April 17, 2017 Hi (@ASadik), 1 hour ago, ASadik said: Hi Pete, Same issue with me. But this B update didn't seem to do the trick. ..... Also I just installed 4955c and that worked fine as well, so for the moment that's what I'm running. The version 4.966b works correct and you should use that in any case. You need to delete the existing controller entries under the [JoyName] section and then run FSX or P3D. If you have both installed you need to delete those entries in both/ any FSUIPC4.ini file ! I.e. here it looked like this and the identical devices have to be deleted (RED marked), or even all if you are not sure. FSUIPC4 will re-arrange the order and correct the Registry for that. [JoyNames] AutoAssignLetters=No 0=Logitech Extreme 3D 0.GUID={0667FA70-5979-11E4-8005-444553540000} 1=vJoy Device 1.GUID={04D9C8B0-994A-11E6-8002-444553540000}2=Saitek Pro Flight Yoke (USB) 2.GUID={B4B9AF80-229C-11E7-8001-444553540000} 3=Saitek Pro Flight Yoke (USB) 3.GUID={B4B9AF80-229C-11E7-8001-444553540000} (It might be different arranged in your case) You will have to check if the previous Button and Axis definition still work, if not it is not an error of FSUIPC4 but the no longer matching of Controller (Joystick) letters that have been changed. Thomas Link to comment Share on other sites More sharing options...
ASadik Posted April 17, 2017 Report Share Posted April 17, 2017 Ok now works fine! Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 17, 2017 Report Share Posted April 17, 2017 9 minutes ago, ASadik said: Ok now works fine! Good. I've now released 4.966c which does that repair automatically! Pete Link to comment Share on other sites More sharing options...
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