Jump to content
The simFlight Network Forums

v4 to v5 transfer with hardware change


Recommended Posts

Hi guys

I just jumped to v5 and also update some hardware parts (mainboard, gpu) together with a fresh windows install. I dropped than my "old" fsuipic6 files from the old disk into the newly installed one. In the sim my profiles are correctly loaded, however all my button and axis assignments seem to be gone within the profile, even they are still there in the .ini file. My flying hardware is all the same as before, no changes there.

Any way to get my old profile back to work without having to assign everything again?

Link to comment
Share on other sites

17 minutes ago, Swissdani said:

Any way to get my old profile back to work without having to assign everything again?

You  haven't supplied your FSUIPC6.INI and .LOG files, which are always necessary for us to help in such cases.

I suspect that you hadn't taken advantage of the facility to assign by Joy Letters instead of ID numbers, but either way a fresh install of Windows and especially  motherboard would result in the GUID numbers changing for all connected devices. Re-matching would be easy with Joy Letters, but it can be figured out in any case with the files you need to provide.

Pete

 

Link to comment
Share on other sites

 

I don't suppose you have the original FSUIPC6.INI file, from before you ran P3D with the new install? That would make this more foolproof.

As it is, these are the assignable devices:

[JoyNames]
AutoAssignLetters=No
0=Bravo Throttle Quadrant
0.GUID={DED29680-1723-11EC-8002-444553540000}
1=TCA Q-Eng 1&2
1.GUID={DED2BD90-1723-11EC-8004-444553540000}
2=Alpha Flight Controls
2.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
3=T.A320 Pilot
3.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
4=CH Pro Pedals USB Rudder Pedals
4.GUID={DEDDBA10-1723-11EC-800D-444553540000}

whilst looking at some axis assignments:

[Axes.Airbus]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=0R,256,F,66818,0,0,0    -{ TO SIM: STEERING_SET }-
3=0S,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
4=1X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
5=1Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
6=1S,256,D,3,0,0,0    -{ DIRECT: Rudder }-
7=2X,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
8=2Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

it appears that:

* the joystick/yoke ID is now 2 (Alpha Flight controls), not 0.
* the rudder ID is now 4 instead of 1
* the throttle quadrant ID is now 0 instead of 2.

That leaves the TCA Q-Eng 1&2 (now 1) and the T.A320 Pilot (now 3). Looking further in the INI there are these axis assignments

[Axes.747]
10=3X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
11=3Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-

Which implies the one of those two as yet determined devices is also a joystick or yoke. If the T.A320 Pilot is a sidestick then my earlier deduction is wrong, and these settings would be more correct:

* the sidestick ID is now 3 (T.A320 Pilot), not 0.
* the rudder ID is now 4 instead of 1
* the throttle quadrant ID is now 0 instead of 2.
* the yoke ID is now 2 instead of 3.

leaving just the TCA Q-Eng 1&2 which must have changed from  4 to 1.

So I think the settings in [JoyNames] should now be:

2=Bravo Throttle Quadrant
2.GUID={DED29680-1723-11EC-8002-444553540000}
4=TCA Q-Eng 1&2
4.GUID={DED2BD90-1723-11EC-8004-444553540000}
3=Alpha Flight Controls
3.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
0=T.A320 Pilot
0.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
1=CH Pro Pedals USB Rudder Pedals
1.GUID={DEDDBA10-1723-11EC-800D-444553540000}

Now you might be successful just changing those lines -- FSUIPC will try to force the ID change in the Registry. But this is not guaranteed. It is probably safer to change  the AutoAssignLetters=No parameter to Yes, then run P3D, and afterwards edit the letters in the [JoyName] section instead of the numbers.

Pete

 

Link to comment
Share on other sites

Hi Pete

I do indeed not have the original ini file with the fresh install, just overwrote ist.

I changed now the JoyNames as suggested by you and yes the T.320 is the Thrustmaster airbus stick. The result after loading the sim is now:

[JoyNames]
AutoAssignLetters=No
2=Alpha Flight Controls
2.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
4=CH Pro Pedals USB Rudder Pedals
4.GUID={DEDDBA10-1723-11EC-800D-444553540000}
3=T.A320 Pilot
3.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
0=Bravo Throttle Quadrant
0.GUID={DED29680-1723-11EC-8002-444553540000}
1=TCA Q-Eng 1&2
1.GUID={DED2BD90-1723-11EC-8004-444553540000}
0.WARNING=This joystick was ID 2, but was duplicated: review and fix assignments, reload settings
1.WARNING=This joystick was ID 4, but was duplicated: review and fix assignments, reload settings
2.WARNING=This joystick was ID 3, but was duplicated: review and fix assignments, reload settings
3.WARNING=This joystick was ID 0, but was duplicated: review and fix assignments, reload settings
4.WARNING=This joystick was ID 1, but was duplicated: review and fix assignments, reload settings
A=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
B=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
C=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>


So the numbers seem have to changed back to the state before I manually edited them.

 

23 minutes ago, Pete Dowson said:

 

I don't suppose you have the original FSUIPC6.INI file, from before you ran P3D with the new install? That would make this more foolproof.

As it is, these are the assignable devices:

[JoyNames]
AutoAssignLetters=No
0=Bravo Throttle Quadrant
0.GUID={DED29680-1723-11EC-8002-444553540000}
1=TCA Q-Eng 1&2
1.GUID={DED2BD90-1723-11EC-8004-444553540000}
2=Alpha Flight Controls
2.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
3=T.A320 Pilot
3.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
4=CH Pro Pedals USB Rudder Pedals
4.GUID={DEDDBA10-1723-11EC-800D-444553540000}

whilst looking at some axis assignments:

[Axes.Airbus]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=0R,256,F,66818,0,0,0    -{ TO SIM: STEERING_SET }-
3=0S,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
4=1X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
5=1Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
6=1S,256,D,3,0,0,0    -{ DIRECT: Rudder }-
7=2X,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
8=2Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

it appears that:

* the joystick/yoke ID is now 2 (Alpha Flight controls), not 0.
* the rudder ID is now 4 instead of 1
* the throttle quadrant ID is now 0 instead of 2.

That leaves the TCA Q-Eng 1&2 (now 1) and the T.A320 Pilot (now 3). Looking further in the INI there are these axis assignments

[Axes.747]
10=3X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
11=3Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-

Which implies the one of those two as yet determined devices is also a joystick or yoke. If the T.A320 Pilot is a sidestick then my earlier deduction is wrong, and these settings would be more correct:

* the sidestick ID is now 3 (T.A320 Pilot), not 0.
* the rudder ID is now 4 instead of 1
* the throttle quadrant ID is now 0 instead of 2.
* the yoke ID is now 2 instead of 3.

leaving just the TCA Q-Eng 1&2 which must have changed from  4 to 1.

So I think the settings in [JoyNames] should now be:

2=Bravo Throttle Quadrant
2.GUID={DED29680-1723-11EC-8002-444553540000}
4=TCA Q-Eng 1&2
4.GUID={DED2BD90-1723-11EC-8004-444553540000}
3=Alpha Flight Controls
3.GUID={DEDD1DD0-1723-11EC-8007-444553540000}
0=T.A320 Pilot
0.GUID={DEDD6BF0-1723-11EC-800A-444553540000}
1=CH Pro Pedals USB Rudder Pedals
1.GUID={DEDDBA10-1723-11EC-800D-444553540000}

Now you might be successful just changing those lines -- FSUIPC will try to force the ID change in the Registry. But this is not guaranteed. It is probably safer to change  the AutoAssignLetters=No parameter to Yes, then run P3D, and afterwards edit the letters in the [JoyName] section instead of the numbers.

Pete

 

 

Link to comment
Share on other sites

3 minutes ago, Swissdani said:

I do indeed not have the original ini file with the fresh install, just overwrote ist.

I changed now the JoyNames as suggested by you and yes the T.320 is the Thrustmaster airbus stick. The result after loading the sim is now:

You seem to have done both at the same time -- changed the IDs and set it to assign joy letters. It was an either/or choice. I hope it isn't now even more of a mess.

Please provide the new INI file, not just the one section.

Note that I am out of the office now till tomorrow. If you want to help yourself to fix it, follow the logic I showed in my earlier reply to change the ID numbers, but now change them to the letters A to E.

Pete

 

Link to comment
Share on other sites

Ok. I forgot to change the ids to the new numbers, but if you just manually remove the warning lines in your ini, just to tidy-up, you should be ok - delete these:

Quote

0.WARNING=This joystick was ID 2, but was duplicated: review and fix assignments, reload settings
1.WARNING=This joystick was ID 4, but was duplicated: review and fix assignments, reload settings
2.WARNING=This joystick was ID 3, but was duplicated: review and fix assignments, reload settings
3.WARNING=This joystick was ID 0, but was duplicated: review and fix assignments, reload settings
4.WARNING=This joystick was ID 1, but was duplicated: review and fix assignments, reload settings

John

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.