Saitek X-55 Rhino Stick-Throttles profile available

[MaltMuncher 0]

For those who aren't afraid of having to reinstall drivers if you mess up and are comfortable in regedit, I replaced any mention of "X-55" under [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001] with X-56 instead other than anything file path related. MFS is now seeing my setup as an X-56 and provided the stock bindings for the X-56.

Here are the XML dumps that were generated when I saved off the control scheme. I named the profile X-55 when I saved it. You will likely have to retain the GUID and ProductID from your file for this to work. Prepare for a wall of text.

 

**********Start of first profile

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="1238"/>
<FriendlyName>Saitek Pro Flight X-55 Rhino Throttle profile</FriendlyName>
<Device DeviceName="Saitek Pro Flight X-56 Rhino Throttle" GUID="{FDABE740-E156-11EA-8004-444553540000}" ProductID="41493">
    <Axes>
        <Axis AxisName="X" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="Y" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="Z" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rX" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rY" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rZ" AxisSensitivy="0" AxisDeadZone="0"/>
    </Axes>
    <Context ContextName="PLANE">
        <Action ActionName="KEY_SPOILERS_TOGGLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 8">7</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_PARKING_BRAKES" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 9">8</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FLAPS_INCR" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 30">29</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FLAPS_DECR" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 31">30</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_ELEV_TRIM_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Z ">1058</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_GEAR_UP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 6">5</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_GEAR_DOWN" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 7">6</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FUEL_PUMP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 1">0</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_MIXTURE_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis X ">1026</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_THROTTLE_AXIS_SET_EX1" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Y ">1042</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_PROP_PITCH_AXIS_SET_EX1" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Z ">802</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="MODES">
        <Action ActionName="KEY_VIEW_MODE" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
    </Context>
</Device>

**********End of first profile

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="1238"/>
<FriendlyName>Saitek Pro Flight X-55 Rhino Stick profile</FriendlyName>
<Device DeviceName="Saitek Pro Flight X-56 Rhino Stick" GUID="{F506EBD0-E156-11EA-8001-444553540000}" ProductID="8725">
    <Axes>
        <Axis AxisName="X" AxisSensitivy="-50" AxisDeadZone="2"/>
        <Axis AxisName="Y" AxisSensitivy="-50" AxisDeadZone="0"/>
        <Axis AxisName="rZ" AxisSensitivy="-50" AxisDeadZone="2"/>
    </Axes>
    <Context ContextName="PLANE">
        <Action ActionName="KEY_AP_MASTER" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 2">1</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_BRAKES" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 5">4</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_ELEVATOR_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Y ">1042</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_AILERONS_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis X ">1026</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_RUDDER_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Z ">802</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FUEL_PUMP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 3">2</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="MODES">
        <Action ActionName="KEY_COCKPIT_RESET" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CYCLE_PILOTVIEW_NEXT" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Up">256</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CYCLE_PILOTVIEW_BACK" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Down">258</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="COCKPIT_GLOBAL_CAMERA">
        <Action ActionName="KEY_COCKPIT_FREELOOK_VRTC_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Y ">786</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_FREELOOK_HRZ_SET" Flag="132">
            <Primary>
                <KEY Information="Joystick R-Axis X ">770</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="EXTERNAL_CAMERA">
        <Action ActionName="KEY_CAMERACHASE_RESET" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW1" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW2" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Down">258</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW3" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW4" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Up">256</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_FREELOOK_VRTC_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Y ">786</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_FREELOOK_HRZ_SET" Flag="132">
            <Primary>
                <KEY Information="Joystick R-Axis X ">770</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="COCKPIT_CAMERA">
        <Action ActionName="KEY_COCKPIT_QUICKVIEW4" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_QUICKVIEW3" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="INSTRUMENTS_CAMERA">
        <Action ActionName="KEY_COCKPIT_CYCLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_BACKCYCLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="SMART_CAMERA">
        <Action ActionName="KEY_TOGGLE_SMART_CAMERA" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 1">0</KEY>
            </Primary>
        </Action>
    </Context>
</Device>

 

****** Enjoy and good luck

[taylortdhouse 0]

2 hours ago, MaltMuncher said:

For those who aren't afraid of having to reinstall drivers if you mess up and are comfortable in regedit, I replaced any mention of "X-55" under [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001] with X-56 instead other than anything file path related. MFS is now seeing my setup as an X-56 and provided the stock bindings for the X-56.

Here are the XML dumps that were generated when I saved off the control scheme. I named the profile X-55 when I saved it. You will likely have to retain the GUID and ProductID from your file for this to work. Prepare for a wall of text.

Spoiler

 

**********Start of first profile

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="1238"/>
<FriendlyName>Saitek Pro Flight X-55 Rhino Throttle profile</FriendlyName>
<Device DeviceName="Saitek Pro Flight X-56 Rhino Throttle" GUID="{FDABE740-E156-11EA-8004-444553540000}" ProductID="41493">
    <Axes>
        <Axis AxisName="X" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="Y" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="Z" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rX" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rY" AxisSensitivy="0" AxisDeadZone="0"/>
        <Axis AxisName="rZ" AxisSensitivy="0" AxisDeadZone="0"/>
    </Axes>
    <Context ContextName="PLANE">
        <Action ActionName="KEY_SPOILERS_TOGGLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 8">7</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_PARKING_BRAKES" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 9">8</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FLAPS_INCR" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 30">29</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FLAPS_DECR" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 31">30</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_ELEV_TRIM_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Z ">1058</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_GEAR_UP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 6">5</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_GEAR_DOWN" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 7">6</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FUEL_PUMP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 1">0</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_MIXTURE_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis X ">1026</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_THROTTLE_AXIS_SET_EX1" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Y ">1042</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_PROP_PITCH_AXIS_SET_EX1" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Z ">802</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="MODES">
        <Action ActionName="KEY_VIEW_MODE" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
    </Context>
</Device>

**********End of first profile

<?xml version="1.0" encoding="UTF-8"?>
<Version Num="1238"/>
<FriendlyName>Saitek Pro Flight X-55 Rhino Stick profile</FriendlyName>
<Device DeviceName="Saitek Pro Flight X-56 Rhino Stick" GUID="{F506EBD0-E156-11EA-8001-444553540000}" ProductID="8725">
    <Axes>
        <Axis AxisName="X" AxisSensitivy="-50" AxisDeadZone="2"/>
        <Axis AxisName="Y" AxisSensitivy="-50" AxisDeadZone="0"/>
        <Axis AxisName="rZ" AxisSensitivy="-50" AxisDeadZone="2"/>
    </Axes>
    <Context ContextName="PLANE">
        <Action ActionName="KEY_AP_MASTER" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 2">1</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_BRAKES" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 5">4</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_ELEVATOR_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis Y ">1042</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_AILERONS_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick L-Axis X ">1026</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_AXIS_RUDDER_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Z ">802</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_FUEL_PUMP" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 3">2</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="MODES">
        <Action ActionName="KEY_COCKPIT_RESET" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CYCLE_PILOTVIEW_NEXT" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Up">256</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CYCLE_PILOTVIEW_BACK" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Down">258</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="COCKPIT_GLOBAL_CAMERA">
        <Action ActionName="KEY_COCKPIT_FREELOOK_VRTC_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Y ">786</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_FREELOOK_HRZ_SET" Flag="132">
            <Primary>
                <KEY Information="Joystick R-Axis X ">770</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="EXTERNAL_CAMERA">
        <Action ActionName="KEY_CAMERACHASE_RESET" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 4">3</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW1" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW2" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Down">258</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW3" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_QUICKVIEW4" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Up">256</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_FREELOOK_VRTC_SET" Flag="4">
            <Primary>
                <KEY Information="Joystick R-Axis Y ">786</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_CHASE_FREELOOK_HRZ_SET" Flag="132">
            <Primary>
                <KEY Information="Joystick R-Axis X ">770</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="COCKPIT_CAMERA">
        <Action ActionName="KEY_COCKPIT_QUICKVIEW4" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_QUICKVIEW3" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="INSTRUMENTS_CAMERA">
        <Action ActionName="KEY_COCKPIT_CYCLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Right">257</KEY>
            </Primary>
        </Action>
        <Action ActionName="KEY_COCKPIT_BACKCYCLE" Flag="2">
            <Primary>
                <KEY Information="Joystick Pov Left">259</KEY>
            </Primary>
        </Action>
    </Context>
    <Context ContextName="SMART_CAMERA">
        <Action ActionName="KEY_TOGGLE_SMART_CAMERA" Flag="2">
            <Primary>
                <KEY Information="Joystick Button 1">0</KEY>
            </Primary>
        </Action>
    </Context>
</Device>

 

 

****** Enjoy and good luck

Do you mind simplifying this for us?  I'm familiar with regedit, but I don't really see anything mentioned about my X-55.  Also for the XML profiles, where would I need to replace those for the Windows Store version?  

Edited August 20, 2020 by taylortdhouse

[MaltMuncher 0]

@taylortdhouse The registry keys reference the driver key if I recall correctly so you won't see any keys titled X-55. I selected [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001] in regedit and then used Ctrl + F to search for X-55 in any subsidiary keys. I updated any keys that reference the X-55 Rhino other than paths to directories which exist to launch the configuration software. Taking a backup of the registry prior to this would probably be wise in case of any issues or mistakes.

With that said, if you overwrite the XML configuration that is created by MFS when you are forced to save a profile after assigning a control, then the regedit changes may not be required. I should mention that the XML files that I speak of will not exist until you have bound a control and saved a profile for the throttle and for the stick.

I have not tried replacing the contents of the XML files as I modified my registry but I used the registry method to get MSF to recognize my X-55 as an X-56 in order to generate the XML so I could share it here.

For me, the XMLs are located in a folder here: C:\Users\your_user_here\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\0009000001AECAB5_00000000000000000000000069F80140.

If that directory does not exist on your computer, go to the appdata folder by entering this in your file explorer address bar.C:\Users\your_user_here\AppData\Local\Packages and search for Microsoft.FlightSimulator. If you have trouble accessing the appdata folder, put % signs around it as it's a hidden folder by default.

In that directory, you will find several directories named with long strings. In each directory, there will be an XML. Open each XML until you find one that references the X-55 throttle and one that references the X-55 stick. They will be in separate directories and separate XML files as they are separate controllers. It is in these XML files that I figure you could paste the configurations that I shared previously. Again, you will likely need to use your GUID and ProductID. If this doesn't work, you could try using the ones that I shared in the configuration. If you already have some work into binding keys, you may want to copy the existing XML files to a backup location.

If you get this method working, please let me know as I'm curious.

Edited August 20, 2020 by MaltMuncher
Clarification

[SledGend 0]

@MaltMuncher - I grok.

You tricked Windows into thinking you had an X-56 installed, and when MSF "saw" that an X-56 was installed, which I guess is a supported device, MSF created the default profile for an X-56. I figure next step is to changes reference in both the XML and the Registry to reflect the X-55, at a minimum so that other games depending on the X-55 still work.

Questions... how did you save the profile to XML - I dont see that option in the PRESET MANAGER. And where is the profiles folder located?

For example I created a profile called X55X55X55X55X55 and did both a Registry and file seach on the system drive (which is also where the game is installed), and I came up with nothing.

I figure if I find the profile, I can swap out the XML with your XML, change references from X-56 to X-55, and I'd be in a good place to customize.

Edited August 20, 2020 by SledGend

[irsmurf 0]

No need for registry edits. While the Microsoft version of Flight Simulator (as opposed to the Steam version) is a pain to modify, it can be done:

Download the "stick" and "throttle" files linked here: https://www.reddit.com/r/MicrosoftFlightSim/comments/ic90xr/x55_success/g21pouh/?utm_source=reddit&utm_medium=web2x&context=3

Extract them to a folder, if downloaded as a zip file.

Connect Joystick and Throttle to your computer.

WINDOWS KEY + R
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\0009000000195F8C_00000000000000000000000069F80140

Jot down the first five characters of each folder name:
<C4FEA> (Note: Anything surrounded by <> is an example only, your generated file/folder names will be distinct.)
<C6D89>
<DA9B0>

You will use these to identify which folders existed before you make new ones, later. Do NOT close this File Explorer window.

Start Flight Simulator
Options
Controls

Click Saitek Pro Flight X-55 Rhino Stick
Click Preset Manager (bottom of screen)
Click +
Name it anything -> OK

ALT-TAB back to File Explorer
Jot down the first five characters of the new folder. This is your Stick folder.
<EAE43>

ALT-TAB back to Flight Simulator
Click Saitek Pro Flight X-55 Rhino Throttle
Click Preset Manager (bottom of screen)
Click +
Name it anything -> OK

ALT-TAB back to File Explorer
Jot down the first five characters of the new folder. This your Throttle folder.
<56F89>

ALT-TAB back to Flight Simulator
Exit Flight Simulator:
Welcome
Exit to Desktop
Yes

Open the Stick folder
Copy the long filename: <A8C17F977B1A4357B4DC511C39D6E542>
Delete the file with the long filename.
Rename the stick file to the above filename.
Move/Copy the new file to the folder from which you just deleted the old file

Open the Throttle folder
Copy the long filename: <39609CD93C314458A241E56267510527>
Delete the file with the long filename.
Rename the throttle file to the above filename.
Move/Copy the new file to the folder from which you just deleted the old file

Close File Explorer. Start Flight Simulator.
Options
Controls

You'll see the profile loaded in for both the Stick and Throttle: Screenshots

[smorency44 0]

18 hours ago, Elkarlo said:

First thanks for the hint with the input folders.

For steam it is: "Steam"\SteamApps\common\Microsoft FlightSimulator\Input\

 

There is already a

Saitek_Pro_Flight_X-56_Rhino_Stick.xml

and

Saitek_Pro_Flight_X-56_Rhino_Throttle.xml

The X55 and the X56 are basically the same Sticks: Simply Copy the xml file and rename the Copy to

Saitek_Pro_Flight_X-55_Rhino_Stick.xml

and

Saitek_Pro_Flight_X-55_Rhino_Throttle.xml

Now open the XML and Change

<Device DeviceName="Saitek Pro Flight X-56 Rhino Stick"

to

<Device DeviceName="Saitek Pro Flight X-55 Rhino Stick"

the same for the throttle of course.

 

Now you have a fully mapped basic setup by Microsoft for your stick.

@Elkarlo - Worked like a charm, I used Notepad++ to edit it but now I'm flying around with my X55 and it works very well, thank you!

[MaltMuncher 0]

@irsmurf One thing that I was trying to get working was to have the image of the controllers show up in the control configuration menu and the quick menu in game. I assume that this is related to the GUID and/or the ProductID.

Do you have any ideas on getting the X-56 controllers to display in the menus? We might have to find an X-56 owner to share their configuration files.

Edit

Scratch that, an individual on the Reddit link that you posted shared the information.

<Device DeviceName="Saitek Pro Flight X-55 Rhino Stick" GUID="745a17a0-74d3-11d0-b6fe-00a0c90f57da" ProductID="2215">

 

<Device DeviceName="Saitek Pro Flight X-55 Rhino Throttle" GUID="745a17a0-74d3-11d0-b6fe-00a0c90f57da" ProductID="A215">

Edited August 20, 2020 by MaltMuncher
Found more information

[Elkarlo 0]

18 hours ago, MaltMuncher said:

@Elkarlo, can you please post a dump of the contents of the Saitek_Pro_Flight_X-56_Rhino_Stick.xml and Saitek_Pro_Flight_X-56_Rhino_Throttle.xml files? We would then be able to paste them into an existing configuration for the Windows 10/Xbox/Gamepass version of the game.

I live in Germany and was at Work, but i see you got the dump. It works for me without the Devicenumbers as MS Flightsim goes after the USB Device Name, not the GUID. That seems the reason for the "phantom" showing short the X56 Config when you start the Simulator and then it parses that you don't have a X-56 but a X-55 and config is gone. With the correct Name MS gives you the Config without needing the GUID and ProductID. But having them is better, so thanks for your effort.

[Rompastomp 0]

Nice thread guys.

One issue I am having with following the instructions is there is no Microsoft.FlightSimulator folder (or anything similar) in my %appdata%.

I have a steam install.

Any guidance appreciated!?

 

[bertduyck 0]

14 hours ago, Rompastomp said:

Nice thread guys.

One issue I am having with following the instructions is there is no Microsoft.FlightSimulator folder (or anything similar) in my %appdata%.

I have a steam install.

Any guidance appreciated!?

 

\steamapps\common\MicrosoftFlightSimulator\Input

[Vonwen 0]

Finally gave in and purchased the game on Steam, I wanted to have it forever anyway and not be reliant on the Game Pass if I ever want to cancel it.

It's shocking how easy it was to setup the X55 following the simple instructions on reddit (editing the xml files in the input folder), while I could never make it work on MS Store, even when following the tutorial step by step. I do wonder why Microsoft makes it so complicated to touch anything, and it's not only for MSFS.

 

So for Steam, open the reddit link from irsmurf's post, view all comments, and check the tutorial by OP. It basically comes down to making copies of the X56 profile xml files, renaming them to X55, and changing the device GUID inside. Then edit another easy to find xml file to have the X56 texture displayed. Works flawlessly.

[Tarl 0]

Hello Guys,

 

I'm also successfull with mapping the X55 following Reddit but when my throttle is on 0 the plane engine stop on all planes. Is it the same for you guys ? If not do you no why I've this problem.

 

Thanks !

[Tfactis 1]

Thanks for all the info, I was finally able to make it work in the sim but the image is still missing

 

[paddyol 1]

On 8/20/2020 at 2:56 PM, irsmurf said:

No need for registry edits. While the Microsoft version of Flight Simulator (as opposed to the Steam version) is a pain to modify, it can be done:

Download the "stick" and "throttle" files linked here: https://www.reddit.com/r/MicrosoftFlightSim/comments/ic90xr/x55_success/g21pouh/?utm_source=reddit&utm_medium=web2x&context=3

Extract them to a folder, if downloaded as a zip file.

Connect Joystick and Throttle to your computer.

WINDOWS KEY + R
%localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\0009000000195F8C_00000000000000000000000069F80140

Jot down the first five characters of each folder name:
<C4FEA> (Note: Anything surrounded by <> is an example only, your generated file/folder names will be distinct.)
<C6D89>
<DA9B0>

You will use these to identify which folders existed before you make new ones, later. Do NOT close this File Explorer window.

Start Flight Simulator
Options
Controls

Click Saitek Pro Flight X-55 Rhino Stick
Click Preset Manager (bottom of screen)
Click +
Name it anything -> OK

ALT-TAB back to File Explorer
Jot down the first five characters of the new folder. This is your Stick folder.
<EAE43>

ALT-TAB back to Flight Simulator
Click Saitek Pro Flight X-55 Rhino Throttle
Click Preset Manager (bottom of screen)
Click +
Name it anything -> OK

ALT-TAB back to File Explorer
Jot down the first five characters of the new folder. This your Throttle folder.
<56F89>

ALT-TAB back to Flight Simulator
Exit Flight Simulator:
Welcome
Exit to Desktop
Yes

Open the Stick folder
Copy the long filename: <A8C17F977B1A4357B4DC511C39D6E542>
Delete the file with the long filename.
Rename the stick file to the above filename.
Move/Copy the new file to the folder from which you just deleted the old file

Open the Throttle folder
Copy the long filename: <39609CD93C314458A241E56267510527>
Delete the file with the long filename.
Rename the throttle file to the above filename.
Move/Copy the new file to the folder from which you just deleted the old file

Close File Explorer. Start Flight Simulator.
Options
Controls

You'll see the profile loaded in for both the Stick and Throttle: Screenshots

I've tried to follow these instructions however when i exit the game and restart it the profiles that i had just put in there dont show up as a profile on my settings in game, if you have any ideas on how to get the x-55 rhino working please help.

 

Cheers

[Tfactis 1]

Hi Paddyol, I had the same trouble...follow all the steps but don't delete the original file, copy the downloaded file from Google drive in to corresponding files that you just created with those 5 codes, it should work.

You open with notepad.

I still don't have the controller displaying, if anybody know how please assist.

Edited August 23, 2020 by Tfactis