skipjack Posted February 9, 2022 Report Share Posted February 9, 2022 I'm using FSUIPC7 latest addition in MSFS with CH Eclipse controller and a few aircraft are listed in my .ini file. All was working fine then none of the aircraft inputs were working in MSFS. I've attached my FSUIPC&.ini file. I reented the inputs for the Cessna Citation CJ4 and it works fine but nothing else is listed FSUIPC7.ini Link to comment Share on other sites More sharing options...
John Dowson Posted February 9, 2022 Report Share Posted February 9, 2022 Only your CH Pedals are now recognised correctly: Quote [JoyNames] A=CH Pro Pedals USB A.GUID={079F94B0-46D4-11E8-8003-444553540000} B=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> B.GUID={D60B49D0-B207-11E9-8001-444553540000} C=CH Eclipse Yoke USB << MISSING JOYSTICK >> C.GUID={D60B49D0-B207-11E9-8001-444553540000} D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> D.GUID={D60B49D0-B207-11E9-8001-444553540000} 0=CH Pro Pedals USB 0.GUID={079F94B0-46D4-11E8-8003-444553540000} 1= 1.GUID={D60B49D0-B207-11E9-8001-444553540000} E= E.GUID={D60B49D0-B207-11E9-8001-444553540000} The name for the yoke cannot be read correctly - it is blank for some reason. This is the second time this week I have seen this issue, no idea what is causing this at the moment. 13 minutes ago, skipjack said: All was working fine then none of the aircraft inputs were working in MSFS. What changed from when it was working until now? How many devices do you have? Id it just the CH yoke and pedals, or do you have another device? I ask as you have assignments to devices B, C, D and E which all look like they are assigned to the yoke, and you have no assignments at all to your pedals. Did you previously lose your assignments to the yoke and then re-assign for some reason? Can you show me your FSUIPC7.log and FSUIPC7.JoyScan.csv files please. John Link to comment Share on other sites More sharing options...
skipjack Posted February 9, 2022 Author Report Share Posted February 9, 2022 Hi John, I only have the ch yoke and pedals. I have had this problem before but at that time I just reassigned the inputs to all my aircraft. FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted February 9, 2022 Report Share Posted February 9, 2022 (edited) 15 minutes ago, skipjack said: I have had this problem before but at that time I just reassigned the inputs to all my aircraft. You shouldn't have done this as all your previous assignments are still available. This occurs if your GUIDs change. Rather than re-assigning everything, you can just update the [JoyNames] section to match the new GUID. I can help with this. Looks like something strange is going on - your xbox 360 controller os being given the same GUID of your CH Eclipse Yoke for some reason. 15 minutes ago, skipjack said: I only have the ch yoke and pedals. Don't you have an xbox 360 controller as well? Can you please respond to this question (may help): Quote Quote All was working fine then none of the aircraft inputs were working in MSFS. What changed from when it was working until now? I will take a look in detail tomorrow and get back to you. John Edited February 9, 2022 by John Dowson Further info added Link to comment Share on other sites More sharing options...
John Dowson Posted February 10, 2022 Report Share Posted February 10, 2022 I don't know why your xbox controller is being given the same GUID (by windows) as your Yoke: Quote ,,,,,,,,,,,, ,,, HIDscanning completed,,,,,,,,, ,,,,,,,,,,,, N, x00, x068E, xC051, ,-1,-1,0, {NULL}, {NULL}, {D60B49D0-B207-11E9-8001-444553540000}, Y, N N, x00, x068E, xC0F2, ,-1,-1,0, {NULL}, {NULL}, {079F94B0-46D4-11E8-8003-444553540000}, Y, N N, x00, x28DE, x11FF, ,-1,-1,0, {NULL}, {NULL}, {D60B49D0-B207-11E9-8001-444553540000}, Y, N Can we try without the xbox controller? Disconnect it (unplug if wired, power off if not) first, then remove the registry entries for this device. To do this, first run regedit and backup your registry (always do this before making registry changes). Then, save the following text as a .reg file (e.g. removeXboxController.reg): Quote Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_28DE&PID_11FF] [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_28DE&PID_11FF] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_28DE&PID_11FF] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_28DE&PID_11FF] Then double click the file (in windows explorer) to tun it and remove the xbox controller registry entries. These will be recreated when you next connect the controller. Once you have done that, reboot, download and use the attached FSUIPC7.ini file (i.e. use this to replace your current one). Then run MSFS/FSUIPC7 (still without connecting your xbox controller) and see if things look ok. If not, show me those 3 files again (FSUIPC7.ini, FSUIPC7.log, FSUIPC7.JoyScan.csv). If everything looks ok, try connecting your xbox controller again - do this with FSUIPC7 shutdown. Once connected, start FSUIPC7 and check your assignments again, Any issues, show me the 3 files. John FSUIPC7.ini Link to comment Share on other sites More sharing options...
skipjack Posted February 10, 2022 Author Report Share Posted February 10, 2022 1 hour ago, John Dowson said: I don't know why your xbox controller is being given the same GUID (by windows) as your Yoke: Can we try without the xbox controller? Disconnect it (unplug if wired, power off if not) first, then remove the registry entries for this device. To do this, first run regedit and backup your registry (always do this before making registry changes). Then, save the following text as a .reg file (e.g. removeXboxController.reg): Then double click the file (in windows explorer) to tun it and remove the xbox controller registry entries. These will be recreated when you next connect the controller. Once you have done that, reboot, download and use the attached FSUIPC7.ini file (i.e. use this to replace your current one). Then run MSFS/FSUIPC7 (still without connecting your xbox controller) and see if things look ok. If not, show me those 3 files again (FSUIPC7.ini, FSUIPC7.log, FSUIPC7.JoyScan.csv). If everything looks ok, try connecting your xbox controller again - do this with FSUIPC7 shutdown. Once connected, start FSUIPC7 and check your assignments again, Any issues, show me the 3 files. John FSUIPC7.ini 14.08 kB · 1 download John I don't have a xbox controller and never had one. Should I make the reg entries changes you sent ? Link to comment Share on other sites More sharing options...
John Dowson Posted February 10, 2022 Report Share Posted February 10, 2022 18 minutes ago, skipjack said: I don't have a xbox controller and never had one. Hmm, very strange... 19 minutes ago, skipjack said: Should I make the reg entries changes you sent ? Yes please. Link to comment Share on other sites More sharing options...
skipjack Posted February 10, 2022 Author Report Share Posted February 10, 2022 2 hours ago, John Dowson said: I don't know why your xbox controller is being given the same GUID (by windows) as your Yoke: Can we try without the xbox controller? Disconnect it (unplug if wired, power off if not) first, then remove the registry entries for this device. To do this, first run regedit and backup your registry (always do this before making registry changes). Then, save the following text as a .reg file (e.g. removeXboxController.reg): Then double click the file (in windows explorer) to tun it and remove the xbox controller registry entries. These will be recreated when you next connect the controller. Once you have done that, reboot, download and use the attached FSUIPC7.ini file (i.e. use this to replace your current one). Then run MSFS/FSUIPC7 (still without connecting your xbox controller) and see if things look ok. If not, show me those 3 files again (FSUIPC7.ini, FSUIPC7.log, FSUIPC7.JoyScan.csv). If everything looks ok, try connecting your xbox controller again - do this with FSUIPC7 shutdown. Once connected, start FSUIPC7 and check your assignments again, Any issues, show me the 3 files. John FSUIPC7.ini 14.08 kB · 1 download John I tried to run it but was informed "cannot import file. not a registry script". I will attach the file I tried to run in file explorer removexboxcontroller.reg Link to comment Share on other sites More sharing options...
John Dowson Posted February 10, 2022 Report Share Posted February 10, 2022 42 minutes ago, skipjack said: I tried to run it but was informed "cannot import file. not a registry script". I will attach the file I tried to run in file explorer You didn't include the first line, which is essential, and you also had additional spaces. Please try the attached. John removexboxcontroller.reg Link to comment Share on other sites More sharing options...
skipjack Posted February 10, 2022 Author Report Share Posted February 10, 2022 45 minutes ago, John Dowson said: You didn't include the first line, which is essential, and you also had additional spaces. Please try the attached. John removexboxcontroller.reg 522 B · 1 download John I ran the .reg file and it worked. I ran MSFS/FSUIPC7 but none of the aircraft assignments were available. when I entered alt+f. Below are attached the three current files FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted February 10, 2022 Report Share Posted February 10, 2022 Yes, still an issue with xbox 360 controller being recognised, an empty device name, and the same id being assigned two two devices....very strange... Could you try the attach FSUIPC7.ini. This may work, if it allows matching on an empty name string - not sure: FSUIPC7.ini Please try that and report back. Also (if that works or not), could you add the following custom logging (Log->Custom) parameter: x200000 Then exit FSUIPC7, restart, exit again, and show me the generated FSUIPC7.log file. Link to comment Share on other sites More sharing options...
skipjack Posted February 10, 2022 Author Report Share Posted February 10, 2022 1 hour ago, John Dowson said: Yes, still an issue with xbox 360 controller being recognised, an empty device name, and the same id being assigned two two devices....very strange... Could you try the attach FSUIPC7.ini. This may work, if it allows matching on an empty name string - not sure: FSUIPC7.ini 14.04 kB · 1 download Please try that and report back. Also (if that works or not), could you add the following custom logging (Log->Custom) parameter: x200000 Then exit FSUIPC7, restart, exit again, and show me the generated FSUIPC7.log file. John FSUIPC7 now works , all assignments are available . I used the above ini file but I don't know how to do the following " add the following custom logging (Log->Custom) parameter: x200000" Link to comment Share on other sites More sharing options...
skipjack Posted February 10, 2022 Author Report Share Posted February 10, 2022 3 hours ago, skipjack said: John FSUIPC7 now works , all assignments are available . I used the above ini file but I don't know how to do the following " add the following custom logging (Log->Custom) parameter: x200000" I assume that there isn't any thing more to do. I'll attach the three files just in case. first let me say thank you for your help and I would like to make a donation to you for all your assistance and knowledge and for the great program FSUIPC has been over the years FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted February 11, 2022 Report Share Posted February 11, 2022 12 hours ago, skipjack said: I assume that there isn't any thing more to do. Well, you can use things as they are but I am still not happy that you have an empty device name for your yoke. We could try forcibly changing the device if in the registry. This may be possible via the ini. Can you try changing your [JoyNames] section to the following: Quote [JoyNames] A=CH Pro Pedals USB A.GUID={079F94B0-46D4-11E8-8003-444553540000} B=CH Eclipse Yoke USB B.GUID={D60B49D0-B207-11E9-8001-444553540000} 0=CH Pro Pedals USB 0.GUID={079F94B0-46D4-11E8-8003-444553540000} 2=CH Eclipse Yoke USB 2.GUID={D60B49D0-B207-11E9-8001-444553540000} Make those changes with FSUIPC7 closed down, then run it once, exit and show me those files again. Thanks. 12 hours ago, skipjack said: I would like to make a donation to you for all your assistance and knowledge and for the great program FSUIPC has been over the years Thanks for the kind offer but no need really - all part of the support service. John Link to comment Share on other sites More sharing options...
skipjack Posted February 11, 2022 Author Report Share Posted February 11, 2022 6 hours ago, John Dowson said: Well, you can use things as they are but I am still not happy that you have an empty device name for your yoke. We could try forcibly changing the device if in the registry. This may be possible via the ini. Can you try changing your [JoyNames] section to the following: Make those changes with FSUIPC7 closed down, then run it once, exit and show me those files again. Thanks. Thanks for the kind offer but no need really - all part of the support service. John 6 hours ago, John Dowson said: Well, you can use things as they are but I am still not happy that you have an empty device name for your yoke. We could try forcibly changing the device if in the registry. This may be possible via the ini. Can you try changing your [JoyNames] section to the following: Make those changes with FSUIPC7 closed down, then run it once, exit and show me those files again. Thanks. Thanks for the kind offer but no need really - all part of the support service. John I made the changes to joy names and we are back to the original problem . no aircraft assignments FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log Link to comment Share on other sites More sharing options...
John Dowson Posted February 11, 2022 Report Share Posted February 11, 2022 Ok, thanks. So changing the id of your yoke also changes the id if your phantom xbox controller. Very strange... I will maybe come back to this when i have more time, but for now, either go back your previous FSUIPC7.ini if you have that saved, or change your [JoyNames] section to the following: Quote [JoyNames] A=CH Pro Pedals USB A.GUID={079F94B0-46D4-11E8-8003-444553540000} B= B.GUID={D60B49D0-B207-11E9-8001-444553540000} 0=CH Pro Pedals USB 0.GUID={079F94B0-46D4-11E8-8003-444553540000} 1= 1.GUID={D60B49D0-B207-11E9-8001-444553540000} If its all working with that (an an empty yoke name), then we can leave it at that (for now). Thanks, John Link to comment Share on other sites More sharing options...
skipjack Posted February 11, 2022 Author Report Share Posted February 11, 2022 All is working again . Thank you Rich Link to comment Share on other sites More sharing options...
John Dowson Posted February 11, 2022 Report Share Posted February 11, 2022 👍 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