Joy name issue after Windows update

[cellular55]

Hi,

planning to install P3D 5 I have updated Windows 7 with Windows 10- Everything seems to be fine with the exception of Joy names in FSUIP5.ini.

Joys names have been messed up: buttons that were mapped on a device are now mapped on another and so on (I have 4 of them so really a mess).

Is there a way to easily map all them to the original situation?

Thanks and kind regards

Joe

 

[John Dowson]

Hi Joe,

yes, it should be possible to re-map them, and relatively straightforward if you are using the JoyLetters facility (see the User manual if you are not familiar).

If you could post your .ini. .log and .Joyscan.csv files I'll take a look for you.

Cheers,

John

[cellular55]

Hi John,

thanks for the prompt reply.

Attached the file, in the mean time I will llok at the manual.

KR

Joe

FSUIPC5_log.txt fsuipc5.ini

[cellular55]

Sorry I forgot a file.. attached here

FSUIPC5.JoyScan.csv

[Pete Dowson]

17 hours ago, cellular55 said:

planning to install P3D 5 I have updated Windows 7 with Windows 10- Everything seems to be fine with the exception of Joy names in FSUIP5.ini.

Joys names have been messed up: buttons that were mapped on a device are now mapped on another and so on (I have 4 of them so really a mess).

Is there a way to easily map all them to the original situation?

Right. I've analysed the files. I am glad to see that you were using Joy Letters as it makes it a lot easier.

Here's what I think. I sorted the [JoyNames] section so that you can see more clearly what is happening:

--------------------------------------------------

First, the Yoke is okay, still "C":

C=Saitek Pro Flight Yoke
C.GUID={28EBBAA0-829A-11E5-800D-444553540000}
0=Saitek Pro Flight Yoke
0.GUID={28EBBAA0-829A-11E5-800D-444553540000}

----------------------------------------------------

Possibly the 4 usb pads have been mixed up by the Windows update. Having the same name and probably the same version number, Windows cannot distinguish then except by the USB socket -- but that information is not transmitted over an update like that. You need to work out which is which (by testing one button on each) then re-letter the entries in the INI to match.

In other words, if you find for example that a button which should show an assignment you made to device G but now shows as device E, make a note that G -> E. When you have a note of all 4 you can edit these lines accordingly. e.g. in the example I gave, change E= and E.GUID= to G= and G.GUID= respectively.

E=usb pad
E.GUID={28EBBAA0-829A-11E5-8002-444553540000}
1=usb pad
1.GUID={28EBBAA0-829A-11E5-8002-444553540000}

F=usb pad
F.GUID={28EBBAA0-829A-11E5-8003-444553540000}
2=usb pad
2.GUID={28EBBAA0-829A-11E5-8003-444553540000}

G=usb pad
G.GUID={28EBBAA0-829A-11E5-8004-444553540000}
3=usb pad
3.GUID={28EBBAA0-829A-11E5-8004-444553540000}

H=usb pad
H.GUID={28EBBAA0-829A-11E5-8001-444553540000}
4=usb pad
4.GUID={28EBBAA0-829A-11E5-8001-444553540000}

---------------------------------------------------

For Rudder you have these assignments to "A" (which is still the Rudder)

61=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
62=AU,256,D,4,0,0,0    -{ DIRECT: Throttle }-

I don't understand why you have a single universal Throttle assigned to the Rudder??? The device A still appears to be correct, so that's not been reassigned.

A=Saitek Pro Flight Rudder Pedals
A.GUID={28EBBAA0-829A-11E5-800C-444553540000}
5=Saitek Pro Flight Rudder Pedals
5.GUID={28EBBAA0-829A-11E5-800C-444553540000}

----------------------------------------------------

The two throttle quadrants are still assigned as throttle quadrants, B and D. If those are the wrong way around now, just change the B=, B.GUID= etc accordingly.

For one Throttle quadrant you have another two Universal Throttles.
Don't you control each throttle separately? Why two Quadrants and only have multiple universal all-engine throttles

71=DY,256,D,4,0,0,0    -{ DIRECT: Throttle }-
72=DZ,256,D,4,0,0,0    -{ DIRECT: Throttle }-

B=Saitek Pro Flight Quadrant
B.GUID={28EBBAA0-829A-11E5-800E-444553540000}
6=Saitek Pro Flight Quadrant
6.GUID={28EBBAA0-829A-11E5-800E-444553540000}

D=Saitek Pro Flight Quadrant
D.GUID={28EBBAA0-829A-11E5-800F-444553540000}
7=Saitek Pro Flight Quadrant
7.GUID={28EBBAA0-829A-11E5-800F-444553540000}

----------------------------------------------------

Finally you have a disconnected Trim Wheel for which I found no assignments anyway:

L=Pro Flight Cessna Trim Wheel
L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000}

and I think this is a leftover from some previous setup, so you can delete it:

K=<< MISSING JOYSTICK >>

------------------------------------

Hope you find this information sufficient. It isn't a difficult job, thanks to the JoyLetter assignment method! 

Pete

 

[John Dowson]

Thanks Pete, was just about to look into this but you beat me to it!

[cellular55]

Hi,

thanks a lot for the reply.

Thanks to that i have solved the issue and adjusted the assignments... I have to check the rudder: I should not have throttle control there

To delete the trim have I to remove these lines?

L=Pro Flight Cessna Trim Wheel
L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000}

K=<< MISSING JOTSTICK >>

Thanks and KR

Joe

 

 

 

[Pete Dowson]

33 minutes ago, cellular55 said:

To delete the trim have I to remove these lines?

L=Pro Flight Cessna Trim Wheel
L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000}

K=<< MISSING JOTSTICK >>

That trim wheel is not even attached, and thee are no assignments to a wheel, either as L or K, so whether you keep those lines or delete them makes no difference.  Delete them for tidiness.

If you ever reconnect it you can make assignments then.

Pete