This are the (new) Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.
At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
[Solved] Cleaning up devices in .ini
I am having a small issue with FSUIPC causing the PMDG 777 to not climb, plus it is not ‘seeing’ my rudder axis. I think I need to clean up my .ini and reset all the device IDs, it’s become a bit of a mess. Pete do I just unplug them all and then run that file you shared before (USB device registry cleaner) then plug them all back? I know I will have to manually re-code my devices in the aircraft profiles but I am fine with that.
Thanks David
[JoyNames]
2=Saitek Pro Flight X-56 Rhino Stick
2.GUID={3F1ACF50-C06B-11EF-8002-444553540000}
A=Saitek Pro Flight X-56 Rhino Stick
A.GUID={3F1ACF50-C06B-11EF-8002-444553540000}
B=WINWING FCU-32
B.GUID={22FAE130-BF84-11EF-8003-444553540000}
C=Saitek Pro Flight X-56 Rhino Throttle
C.GUID={7FB2E980-C06B-11EF-8004-444553540000}
E=Bravo Throttle Quadrant
E.GUID={6342F1B0-BFA7-11EF-8001-444553540000}
F=TCA YOKE BOEING
F.GUID={6E68F2B0-BFA7-11EF-8002-444553540000}
G=Controller (Afterglow Gamepad for Xbox 360)
G.GUID={8ABFE450-BFA7-11EF-8003-444553540000}
H=MFG Crosswind V2
H.GUID={DA420C30-BF82-11EF-8002-444553540000}
D=WINWING FCU-32 + EFIS-32L
D.GUID={0F8A5100-C2CA-11EF-8001-444553540000}
3=Saitek Pro Flight X-56 Rhino Throttle
3.GUID={7FB2E980-C06B-11EF-8004-444553540000}
J=WINWING MCDU-32-CAPTAIN
J.GUID={327F5FD0-1FB7-11F0-8001-444553540000}
K=WINWING PAP-3
K.GUID={DBEF4720-4B94-11F0-8001-444553540000}
L=WINWING PFP-3N-CAPTAIN
L.GUID={FB82B550-4C74-11F0-8001-444553540000}
4=MFG Crosswind V2
4.GUID={6342F1B0-BFA7-11EF-8001-444553540000}
6=WINWING PAP-3
6.GUID={8ABFE450-BFA7-11EF-8003-444553540000}
5=TCA YOKE BOEING
5.GUID={6E68F2B0-BFA7-11EF-8002-444553540000}
M=WINWING 3N PDC L
M.GUID={133181D0-AB8F-11F0-8001-444553540000}
1=WINWING PAP-3
1.GUID={DBEF4720-4B94-11F0-8001-444553540000}
7=WINWING PFP-3N-CAPTAIN
7.GUID={FB82B550-4C74-11F0-8001-444553540000}
8=Bravo Throttle Quadrant
8.GUID={133181D0-AB8F-11F0-8001-444553540000}
N=MFG Crosswind V2
N.GUID={6342F1B0-BFA7-11EF-8001-444553540000}
P=WINWING PAP-3
P.GUID={8ABFE450-BFA7-11EF-8003-444553540000}
Q=Bravo Throttle Quadrant
Q.GUID={133181D0-AB8F-11F0-8001-444553540000}Posted by: @baw242I am having a small issue with FSUIPC causing the PMDG 777 to not climb
This is usually due to flaps (or maybe spoiler) calibration in FSUIPC. Please see the following post:
https://fsuipc.com/community/fsuipc7-support/climb-performance-pmdg-77er-in-msfs2020/
Posted by: @baw242plus it is not ‘seeing’ my rudder axis. I think I need to clean up my .ini and reset all the device IDs, it’s become a bit of a mess. P
To clean-up your, just delete the following entries:
B=WINWING FCU-32
B.GUID={22FAE130-BF84-11EF-8003-444553540000}
D=WINWING FCU-32 + EFIS-32L
D.GUID={0F8A5100-C2CA-11EF-8001-444553540000}
E=Bravo Throttle Quadrant
E.GUID={6342F1B0-BFA7-11EF-8001-444553540000}
G=Controller (Afterglow Gamepad for Xbox 360)
G.GUID={8ABFE450-BFA7-11EF-8003-444553540000}
H=MFG Crosswind V2
H.GUID={DA420C30-BF82-11EF-8002-444553540000}
J=WINWING MCDU-32-CAPTAIN
J.GUID={327F5FD0-1FB7-11F0-8001-444553540000}
M=WINWING 3N PDC L
M.GUID={133181D0-AB8F-11F0-8001-444553540000}
Posted by: @baw242Pete do I just unplug them all and then run that file you shared before (USB device registry cleaner) then plug them all back? I know I will have to manually re-code my devices in the aircraft profiles but I am fine with that.
Pee retired 5+ years ago now.
I wouldn’t do that. First clean-up your ini, as indicated, then run FSUIPC, exit, then attach your FSUIPC7.ini and FSUIPC7.log files. You probably have a duplicate id. You can remove the entries from your registry for the devices with the same id if you like, or you can try changing the ids using the JoyIds program if you have that. I can provide you with a .reg file again to do this, but I am now on holiday and won’t have much time before the 28thg December.
John
Thanks John, I have deleted those entries and also corrected all the button/axis references to the newer joystick letters. I ran FSUIPC and the log and ini is attached. I haven’t gone into the sim yet to do the calibration fixes but will try tomorrow. Thanks again. David
Posted by: @baw242I have deleted those entries and also corrected all the button/axis references to the newer joystick letters.
But there shouldn’t have been any assignments to those letters – if there were, there should have been a ‘Missing Joystick’ message logged against the entry. Now you have this message on joyletter E – you should change any assignments using that to Q and delete that line.
Your log shows an issue with Joy ID 1 which is used by the following devices:
WINWING 3N PDC L
WINWING PAP-3
Unplug those devices, run the attached script to remove the registry entries for those devices, reboot and then re-attach them.
[Note that you need to rename that script to removeDevices.reg after download – can’t attach .reg files directly at the moment…]
Thats it from me now for a while – I may take a look at support in a couple of days, but not back until the 28th). Any issues, please attach your files (and also maybe your JoyScan.csv file).
John
All sorted John, thanks again. Devices reassigned with new letters and I manually changed the various buttons and axis assignments to the new letters and all working as before.
Hi again John, unfortunately I spoke too soon. The flaps issue is sorted as I removed them from calibration in FSUIPC. But the issues of Joystick identifications persist. I am attaching the three files requested.
What is happening is that the letter identifiers for the Bravo and MFG are getting mixed up, and duplicated. There are slight differences in the issues between the two devices:
Bravo
In FSUIPC app when I try to identify the Bravo to assign buttons and axes it shows as letter J in the app (assigned to a different device in the .ini), but the Bravo is device D in the .ini file. Changing all the button codes in .ini manually to J does actually work, despite the .ini showing it as letter D.
MFG
This device is simply not seen by FSUIPC app at all, searching for axes and then using the rudder pedals does nothing. The device works fine in MSFS, I have now reverted to assigning it in MSFS and not FSUIPC. I wanted to use FSUIPC as I want different sensitivites between Fenix (straight line) and PMDG (curves).
Please could you let me know how I can properly clean the USB devices and .ini and maybe start again, I don’t mind manually editing the buttons and axis assignments in .ini once all the device letter assignments have stabilised.
Note I have a lot of USB devices and don’t attach them all at once, I have the Wingwing A320 MCDU, B737 FMC, B737 EFIS and MCP, plus WingFlex x 3 (A320 EFIS, MCP, Radio), Bravo Throttle, Boeing Yoke, Saitek X56 Joystick and Saitek X56 Throttle, Gamepad and MFG Rudder. 13 devices in total.