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

Notifications

Clear all

[Solved] Cleaning up devices in .ini

BAW242 · 2025-12-22T17:00:27Z

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}

Page 3 / 3 Prev

Posts: 10

BAW242

Registered

Topic starter

December 30, 2025 2:32 pm

(@baw242)

Joined: 1 month ago

I did and the X56 devices are fine (they always behaved despite the issues in the background with the GUIDs). The Bravo now properly identifies as device D for buttons but weirdly the flap axis shows as D in the app, but when I assign it to flaps it still shows as device J in the .ini. It all works fine now but let me know if you think I need to some more cleaning. Files attached.

Attachment : FSUIPC7.ini

Attachment : FSUIPC7.JoyScan.csv

Attachment : FSUIPC7.log

Posts: 173

FSUIPC Support

Moderator

December 30, 2025 5:07 pm

(@fsuipc-support)

Joined: 3 months ago

Looks good to me!

Posted by: @baw242
↑
The Bravo now properly identifies as device D for buttons but weirdly the flap axis shows as D in the app, but when I assign it to flaps it still shows as device J in the .ini.

I don’t think that can be the case. You have flaps assigned to both device D and J, and also F (TCA YOKE BOEING):

[Axes.B737]
RangeRepeatRate=10
0=DZ,256,F,66534,0,0,0 -{ TO SIM: AXIS_FLAPS_SET }-
1=JZ,256,F,66534,0,0,0 -{ TO SIM: AXIS_FLAPS_SET }-

[Axes.A300]
RangeRepeatRate=10
0=DZ,256,F,66534,0,0,0 -{ TO SIM: AXIS_FLAPS_SET }-
1=FZ,256,F,66534,0,0,0 -{ TO SIM: AXIS_FLAPS_SET }-

[Axes.B777]
RangeRepeatRate=10
2=DZ,256,D,23,0,0,0 -{ DIRECT: Flaps }-

[Axes.iFly]
RangeRepeatRate=10
0=DZ,256,F,66534,0,0,0 -{ TO SIM: AXIS_FLAPS_SET }-

Probably better to remove / delete those entries for devices J and F – generally not a good idea to have multiple axis assigned to the same axis control (unless for pilot / co-pilot).

This post was modified 2 weeks ago 2 times by FSUIPC Support