• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Saitek X55

I've recently started flying CFS3 again and got it set up with my trusty logitech G940, force feedback and all that, very nice for a couple of weeks until it "gave up" shall we say.

Any way I now have a Saitek [Logitech] X56 and I must admit its been a bit of a pain to get set up, especially the throttle, what I found was that in the CFS3 Axis settings the rotary on top of the throttle was being assigned to the throttle input, I deleted this input altogether then set about assigning the actual throttles to the Axis_Throttle input.

I found that just moving the throttles did nothing at all, I had to actually "bang" them back and forth off their stops to get an axis response [X Axis]. Now I dont know if this is how its supposed to work with these Saitek throttles but I've made multiple profiles for testing purposes and every time this is the only way I can get the throttle mapped properly.

This is what my .xca entry looks like;

<Device Type="Saitek Pro Flight X-56 Rhino Throttle">
<GameMode Name="Player">
<Axis ID="X" Action="AXIS_THROTTLE_SET" Scale="64" Nullzone="36"/>

Hopefully this can be of some help to you or anyone else using these throttles.
 
Startling! That was my reaction to the word "trusty" used in relation to the other words "Logitech G940". To quote the comic store guy from the Simpsons, "worst Hotas ever!" :biggrin-new:
 
My son also seems to have solved the X55 throttle issue by adjusting the .xca file. More later
 
Last edited:
In fact it's the same as suggested by Ratrace.:applause:


We want to delete the X and Y entries and replace those with the one. More interesting is that I've never bothered to configure through CFS3 but only through the Saitek/Madkatz program. Seems doing it through the CFS3 might be worth investigating.

OLD
</Device> <Device Type="Saitek Pro Flight X-55 Rhino Throttle">
<GameMode Name="Player">
<Axis ID="X" Action="Set_Bank" Scale="64" Nullzone="36"/>
<Axis ID="Y" Action="Set_Pitch" Scale="64" Nullzone="36"/>
<Axis ID="Throttle" Action="AXIS_THROTTLE_SET" Scale="127" Nullzone="1"/>
<Axis ID="Rudder" Action="Set_Yaw" Scale="64" Nullzone="36"/>
<Button ID="1" Action="Fire_Guns"/>
<Button ID="2" Action="FireCannonsOnly"/>
<Button ID="3" Action="ReleaseFireWeapon"/>
<Button ID="4" Action="SelectNextWeapon"/>
<Button ID="5" Action="FLAPS_INCR"/>
<Button ID="6" Action="FLAPS_DECR"/>
<Button ID="7" Action="NextTarget"/>
<Pov ID="1" Action="HeadPov"/>
<Button ID="8" Action="TogglePadlock"/>


New XCA entry



</Device>
<Device Type="Saitek Pro Flight X-55 Rhino Throttle">
<GameMode Name="Player">
<Axis ID="X" Action="AXIS_THROTTLE_SET" Scale="127" Nullzone="1"/>
<Button ID="1" Action="Fire_Guns"/>
<Button ID="2" Action="FireCannonsOnly"/>
<Button ID="3" Action="ReleaseFireWeapon"/>
<Button ID="4" Action="SelectNextWeapon"/>
<Button ID="5" Action="FLAPS_INCR"/>
<Button ID="6" Action="FLAPS_DECR"/>
<Button ID="7" Action="NextTarget"/>
<Pov ID="1" Action="HeadPov"/>
<Button ID="8" Action="TogglePadlock"/>
</GameMode>
 
Back
Top