Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Copy old FSUIPC files into new system

Featured Replies

I have purchased a new computer. For FSUIPC I did this. Copy the old fsuipc.ini file and my .mcry files into the new FSUIPC installation. None of my previous assignment seem to work. Why should they not ?
Have I made it to simple for me ? Or could I have missed something ?

52 minutes ago, jfri said:

I have purchased a new computer. For FSUIPC I did this. Copy the old fsuipc.ini file and my .mcry files into the new FSUIPC installation. None of my previous assignment seem to work. Why should they not ?
Have I made it to simple for me ? Or could I have missed something ?

I think the best place to get help with this is on the FSUIPC7 support forum. John Dowson is very responsive.

https://forum.simflight.com/forum/183-fsuipc7-msfs/

EDIT:  Just saw John Dowson is on vacation until 3 Jan.  "Murphy" strikes again!

Al

Edited by ark

  • Author
Just now, ark said:

I think the best place to get help with this is on the FSUIPC7 support forum. John Dowson is very responsive.

https://forum.simflight.com/forum/183-fsuipc7-msfs/

Al

Not before January 3 2023 so I see if maybe someone here could help me before that.

  • Moderator

The assignments are linked to the GUID of the individual control. Those are noted in the ini file. When you change computers, the GUID is "reissued" by the system and is never the same as in the ini file. Your assignments will not work. Also you didn't say whether you used Profiles or not, your individual aircraft assignments are stored in the Profiles - you would also need to copy them.

Look in the ini file under JoyNames - that may give you an idea how to manually realign the controls.

 

RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti
40" 4K Monitor 3840x2160 

  • Author
30 minutes ago, vgbaron said:

The assignments are linked to the GUID of the individual control. Those are noted in the ini file. When you change computers, the GUID is "reissued" by the system and is never the same as in the ini file. Your assignments will not work. Also you didn't say whether you used Profiles or not, your individual aircraft assignments are stored in the Profiles - you would also need to copy them.

Look in the ini file under JoyNames - that may give you an idea how to manually realign the controls.

I make individual assigment for different planes

In my fsuipc are these lines

[JoyNames]
5=Throttle - HOTAS Warthog
5.GUID={C621E010-7FF4-11ED-800E-444553540000}
E=Throttle - HOTAS Warthog << MISSING JOYSTICK >>
E.GUID={9E6C27E0-EE9A-11E4-8001-444553540000}
L=Throttle - HOTAS Warthog
L.GUID={C621E010-7FF4-11ED-800E-444553540000}

Why three entries ? I suppose MISSING JOYSTICK means the GUID is from the old system. Could I copy that old GUID to the 5 entries or the other way around ?

  • Author

EDIT the third entrie was because I manually assigned two axes

If you temporarily rename your FSUIPC.ini file, then run the sim again, the new ini file it builds will contain the new GUIDs for the HID devices.  If you then overwrite the old GUIDs by copy/pasting the new GUIDs into the old ini file it should work again. 

I've done that before when rebuilding systems here.

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

9 hours ago, Bob Scott said:

If you temporarily rename your FSUIPC.ini file, then run the sim again, the new ini file it builds will contain the new GUIDs for the HID devices.  If you then overwrite the old GUIDs by copy/pasting the new GUIDs into the old ini file it should work again. 

I've done that before when rebuilding systems here.

Brilliant 

Wayne such

Asus Hero Z690, Gigabyte Aorus Master 5080, I914900K, Kraken 360 AIO CPU Cooled, 96 GIGS Corsair DDR5, 32 Inch 4K by 3

  • Author
On 12/23/2022 at 2:46 AM, Bob Scott said:

If you temporarily rename your FSUIPC.ini file, then run the sim again, the new ini file it builds will contain the new GUIDs for the HID devices.  If you then overwrite the old GUIDs by copy/pasting the new GUIDs into the old ini file it should work again. 

I've done that before when rebuilding systems here.

For some reason this does not work for me. My current fsuipc.ini looks like this with the GUID that was generated after deleting fsuipc.ini

[JoyNames]
0=CH THROTTLE QUADRANT
0.GUID={C620A790-7FF4-11ED-8006-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
2=Joystick - HOTAS Warthog
2.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
3=Pro Flight Cessna Trim Wheel
3.GUID={C62191F0-7FF4-11ED-800C-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={C621E010-7FF4-11ED-800E-444553540000}
A=CH THROTTLE QUADRANT
A.GUID={C620A790-7FF4-11ED-8006-444553540000}
B=Saitek Pro Flight Rudder Pedals
B.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
C=Joystick - HOTAS Warthog
C.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
D=Pro Flight Cessna Trim Wheel
D.GUID={C62191F0-7FF4-11ED-800C-444553540000}
E=Throttle - HOTAS Warthog
E.GUID={C621E010-7FF4-11ED-800E-444553540000}

My old fsuipc partly had these entries

[JoyNames]
0=CH Throttle Quadrant USB
0.GUID={67014930-8C74-11E4-8004-444553540000}
2=Saitek Pro Flight Cessna Trim Wheel
2.GUID={FF316550-86D9-11E4-8001-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={9E6C27E0-EE9A-11E4-8001-444553540000}
A=CH Throttle Quadrant USB
A.GUID={67014930-8C74-11E4-8004-444553540000}
C=Saitek Pro Flight Cessna Trim Wheel
C.GUID={FF316550-86D9-11E4-8001-444553540000}
D=Joystick - HOTAS Warthog << MISSING JOYSTICK >>
D.GUID={1CCA0460-D88C-11E4-8001-444553540000}
E=Throttle - HOTAS Warthog
E.GUID={9E6C27E0-EE9A-11E4-8001-444553540000}
1=Flight Rudder Pedals
1.GUID={4FD23130-1375-11ED-8001-444553540000}
F=Flight Rudder Pedals
F.GUID={4FD23130-1375-11ED-8001-444553540000}

EDIT FORGET I had missed copy over some parts of the old ini file

Edited by jfri
Update

Assuming you are using the alpha joynames in the old ini (in this case A,C,D,E,F), you'd want to edit the alpha definitions in the new file so that the devices match:

[JoyNames]
0=CH THROTTLE QUADRANT
0.GUID={C620A790-7FF4-11ED-8006-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
2=Joystick - HOTAS Warthog
2.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
3=Pro Flight Cessna Trim Wheel
3.GUID={C62191F0-7FF4-11ED-800C-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={C621E010-7FF4-11ED-800E-444553540000}
A=CH THROTTLE QUADRANT
A.GUID={C620A790-7FF4-11ED-8006-444553540000}
C=Pro Flight Cessna Trim Wheel
C.GUID={C62191F0-7FF4-11ED-800C-444553540000}
D=Joystick - HOTAS Warthog
D.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
E=Throttle - HOTAS Warthog
E.GUID={C621E010-7FF4-11ED-800E-444553540000}
F=Saitek Pro Flight Rudder Pedals
F.GUID={C620CEA0-7FF4-11ED-8008-444553540000}

This way anything referencing axes or buttons on joystick "A" in the old file will now persistently reference the new GUID assigned to that device.

Also, you do not want auto-assignment of the alpha names to be on.

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • Author
12 minutes ago, Bob Scott said:

Assuming you are using the alpha joynames in the old ini (in this case A,C,D,E,F), you'd want to edit the alpha definitions in the new file so that the devices match:

[JoyNames]
0=CH THROTTLE QUADRANT
0.GUID={C620A790-7FF4-11ED-8006-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
2=Joystick - HOTAS Warthog
2.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
3=Pro Flight Cessna Trim Wheel
3.GUID={C62191F0-7FF4-11ED-800C-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={C621E010-7FF4-11ED-800E-444553540000}
A=CH THROTTLE QUADRANT
A.GUID={C620A790-7FF4-11ED-8006-444553540000}
C=Pro Flight Cessna Trim Wheel
C.GUID={C62191F0-7FF4-11ED-800C-444553540000}
D=Joystick - HOTAS Warthog
D.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
E=Throttle - HOTAS Warthog
E.GUID={C621E010-7FF4-11ED-800E-444553540000}
F=Saitek Pro Flight Rudder Pedals
F.GUID={C620CEA0-7FF4-11ED-8008-444553540000}

This way anything referencing axes or buttons on joystick "A" in the old file will now persistently reference the new GUID assigned to that device.

Also, you do not want auto-assignment of the alpha names to be on.

They already match. Also note my EDIT. I have missed to copy some parts of the old ini file to the new. Now there are working assignments although some axes seem messed up for some reason.

What do you mean by auto assigment ? Both numbers and letter entries was created for me. I don't know why there are double entries

There are two assignments--a numeric one automatically created by FSUIPC, and an alpha one (letter) that is paired with the system-assigned numeric assignment by matching its GUID.  It's possible for the numeric assignments to change from one session to the next (e.g. if you plug the device into a different USB port), but the alpha assignment will always pair up based on the GUID regardless of the numeric assignment.  This is what allows you to create persistent assignments that do not change.

And, no, they don't match.  In your old ini, joystick C was the Saitek trim wheel, in your new one joystick C is the HOTAS Warthog.  In the old ini joystick D was the Warthog and in the new joystick D is the trim wheel, etc.

There's an option in FSUIPC that has it auto-assign joystick names.  That should be turned off when you're manually assigning the joystick names.

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • Author
31 minutes ago, Bob Scott said:

There are two assignments--a numeric one automatically created by FSUIPC, and an alpha one (letter) that is paired with the system-assigned numeric assignment by matching its GUID.  It's possible for the numeric assignments to change from one session to the next (e.g. if you plug the device into a different USB port), but the alpha assignment will always pair up based on the GUID regardless of the numeric assignment.  This is what allows you to create persistent assignments that do not change.

And, no, they don't match.  In your old ini, joystick C was the Saitek trim wheel, in your new one joystick C is the HOTAS Warthog.  In the old ini joystick D was the Warthog and in the new joystick D is the trim wheel, etc.

There's an option in FSUIPC that has it auto-assign joystick names.  That should be turned off when you're manually assigning the joystick names.

I find no option in FSUIPC for auto assign joystick names

At any rate I edited fsuipc.ini for it to match and that was not changed. My entries now is these

[JoyNames]
0=CH THROTTLE QUADRANT
0.GUID={C620A790-7FF4-11ED-8006-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
2=Joystick - HOTAS Warthog
2.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
3=Pro Flight Cessna Trim Wheel
3.GUID={C62191F0-7FF4-11ED-800C-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={C621E010-7FF4-11ED-800E-444553540000}
A=CH THROTTLE QUADRANT
A.GUID={C620A790-7FF4-11ED-8006-444553540000}
F=Saitek Pro Flight Rudder Pedals
F.GUID={C620CEA0-7FF4-11ED-8008-444553540000}
D=Joystick - HOTAS Warthog
D.GUID={C6216AE0-7FF4-11ED-800B-444553540000}
C=Pro Flight Cessna Trim Wheel
C.GUID={C62191F0-7FF4-11ED-800C-444553540000}
E=Throttle - HOTAS Warthog
E.GUID={C621E010-7FF4-11ED-800E-444553540000}

My old entries had CH Pro Pedals for B. These pedals I don't have anymore

2 hours ago, jfri said:

I find no option in FSUIPC for auto assign joystick names

Here is what I have in my FSUJIPC7.ini file, probably a holdover from P3D. I have assigned controller letters manually that make sense to me.

[JoyNames]
AutoAssignLetters=No

.....  the controller GUID assignments then are here .....

Also, FYI, page 21 of the FSUIPC Users Guide says:

Keeping track of multiple control devices ("Joy Letters")
The “Joy Letters” facility is now activated by default in FSUIPC7, and so letters will be automatically assigned to your
devices. If you wish to assign your own letters, you can change the assigned letter by editing your FSUIPC7.ini. It is
recommended to do this before you start assigning to the device, otherwise you will also need to change the joyletter
used in those assignments. In general you would choose letters suggesting the type of control—J for Joystick, Y for
Yoke, T for throttle or Q for Quadrant, G for G-stick, etc.

 

Al

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.