X55 Rhino Button Layout with Reference Card

... since you're using the Saitek software, how about my question above? ;) Can you change the throttle curve with the mode switch? I.e. can you have mode 1 be 0-100% and mode 2 be -100 to +100

Unfortunately not. The mode switch only affects the three bottom switches. But I have reverse toggle at my index finger when holding the throttle, so it's very easy to go in reverse anyways.
 
I've been fiddling with the software that comes with this stick to see whether I can use it to assign some ED 'macros' to buttons and switches. I offer here a prototype 'Docking Request' HUD profile, containing a macro bound to the SW6 switch.

To make it work with your Rhino there are few constraints.

  1. It sends key presses to the game to open the targets panel, tab to Contacts, then issue the docking request
  2. It assumes that when you open the targets panel, that the Navigation tab is active
  3. When the macro ends, it makes the Navigation tab active again (so it will work the next time you use it)
  4. It 'toggles'. If you already have permission to dock, it cancels the request.
  5. The keys used in the macro must be bound in your ED custom.binds file. I have used the default Keyboard UI controls Q,W,E,A,S,D,<space> that display in the game help screens.
  6. To work properly, you need to have the X-55 'HUD' software installed and running, with the profile loaded

At the link, there is a copy of the X-55 HUD profile, ED custom.binds file that includes the key bindings so the HUD macro works, and an HTML file that shows the other bindings used by the stick/throttle. All 3 files are also in a zip file if you prefer to download that.

Hope some people find it useful, I'd welcome feedback. Currently the profile has a 0.2 second delay between key presses so you can see it working.

To use it, you must have the station set as your target. Then hold down the SW6 switch until the docking request is sent. Releasing the switch then resets the target panel back to the Nvigation tab, and closes the tab.

https://drive.google.com/folderview?id=0B_b1val4v4WBckJTWnRPVFRKY0U&usp=sharing

(I think you may need a google account to use that link).

Be wary; if this gets the tabbing wrong it can abandon contracts instead. I raised a request thread for a key bind for requesting docking but nothing yet.
 
Have no HUD on the X55, but yes, I programmed all the buttons as the default keybinds from the game. That also means that I basically only have to map the axis in the game, if my keybinds would get wiped with some update or such. :)

H.U.D Software is what Saitek refer to themselves. http://www.saitek.com/manuals/X55_Manual_Complete.pdf I assume you're using that to be able to use the modes on the throttle?
If so, would you mind sharing the .pr0 file please and your custom.binds file from ED?
 
Be wary; if this gets the tabbing wrong it can abandon contracts instead. I raised a request thread for a key bind for requesting docking but nothing yet.

Apologies for that! I also asked for a key bind for docking, but I can now achieve a docking request in a couple of seconds using just ED bindings and no use of the Saitek software at all.
 
Anybody know if there is a technical reason for FD not to natively support the slider on the Throttle in ED?

Or should it be reported as a bug?
 
Perhaps as an enhancement request? It doesn't support the mouse 'nipple' or the mode switch either.

Yeah I know, but I can imagine that the mouse nipple and mode switch are somewhat of an oddity and take much more time and effort to implement natively.
The slider however is just a switch with two positions.


Apologies for that! I also asked for a key bind for docking, but I can now achieve a docking request in a couple of seconds using just ED bindings and no use of the Saitek software at all.


Could you please share that?
 
Last edited:
Anybody know if there is a technical reason for FD not to natively support the slider on the Throttle in ED?

Or should it be reported as a bug?

Here's the thing, on the aircraft used as a model for this that switch is used for the speedbrake; forward to deploy it, back to retract it. E : D doesn't have a comparable function, so I don't see reason for the devs to write something for it when they have a million other things to do. Anything you want it to do in the game is a matter of keystrokes, and that can be managed in the software for it - aside toggling jump modes. I set two of the guarded switches at the bottom for that though, one for supercruise and the other for hyperdrive.
 
Could you please share that?

Away from decent IT at the mo. But from memory I have the H4 rocker on the throttle mapped so that

Up brings up the Target Panel
Right and Left tab through Navigation, Transactions, etc

When target panel is 'open' then on the joy stick, the castle hat becomes up/down/left right in the UI and the main trigger button is select. (Note that the Rhino buttons/triggers/switches can be assigned to do different things depending on whether any panels are open)

So to request docking

H4 Up
H4 left/right to select the correct tab
Fire on joystick
up/down on castle hat to select station
Fire
Down on castle hat then fire to select 'Request docking'
Up+Up on H4 to return to cockpit view

Something like that! It's consigned to 'muscle memory' now. It's takes me less than a second.

- - - - - Additional Content Posted / Auto Merge - - - - -

Here's the thing, on the aircraft used as a model for this that switch is used for the speedbrake; forward to deploy it, back to retract it. E : D doesn't have a comparable function, ...

I think it would be perfect as the toggle for whether the throttle is for forward or reverse speed.
 
Away from decent IT at the mo. But from memory I have the H4 rocker on the throttle mapped so that

Up brings up the Target Panel
Right and Left tab through Navigation, Transactions, etc

When target panel is 'open' then on the joy stick, the castle hat becomes up/down/left right in the UI and the main trigger button is select. (Note that the Rhino buttons/triggers/switches can be assigned to do different things depending on whether any panels are open)

So to request docking

H4 Up
H4 left/right to select the correct tab
Fire on joystick
up/down on castle hat to select station
Fire
Down on castle hat then fire to select 'Request docking'
Up+Up on H4 to return to cockpit view

Something like that! It's consigned to 'muscle memory' now. It's takes me less than a second.

- - - - - Additional Content Posted / Auto Merge - - - - -



I think it would be perfect as the toggle for whether the throttle is for forward or reverse speed.



Thanks for taking the trouble to explain.
repped
 
Here's the thing, on the aircraft used as a model for this that switch is used for the speedbrake; forward to deploy it, back to retract it. E : D doesn't have a comparable function, so I don't see reason for the devs to write something for it when they have a million other things to do. Anything you want it to do in the game is a matter of keystrokes, and that can be managed in the software for it - aside toggling jump modes. I set two of the guarded switches at the bottom for that though, one for supercruise and the other for hyperdrive.


The mere fact that the ED ships have no comparable function to the switch in the aircraft after which it is originally modeled could not be the reason for ignoring it.
There are many switches that have no comparable function. Added to that there are also many functions in the game that are not present in real life planes and therefore many switches will be mapped as the user sees fit anyway.
It simply is a useful switch like any other switch on the throttle that can be used for many functions.
Just like DRY411S already stated it is perfect for switching between forward and backward thrust and that is what I want to use it for.
It would have been great if FD would not have ignored the switch. If it is a deliberate decision... I feel that is a weird thing to do.
I can use the Saitek software, but getting used to that will take some time.
 
Last edited:
I can use the Saitek software, but getting used to that will take some time.

I have found that it is possible to use both simultaneously, but it is sensitive to the order than you start up things. For example in E:D you can map the forward/backward toggle to a key in a custom.binds, then assign the switch to that key press. But it's messy to do, run and maintain, having bindings in 2 separate places, with hard linkages between them.
 
Last edited:
I have found that it is possible to use both simultaneously, but it is sensitive to the order than you start up things. For example in E:D you can map the forward/backward toggle to a key in a custom.binds, then assign the switch to that key press. But it's messy to do, run and maintain, having bindings in 2 separate places, with hard linkages between them.

Yes, that is why I would have liked to go the easy road.
I intend to master the Saitek software eventually, because I watched a youtube video by a guy called Frooglesim in which he demonstrated the customization power that is in the software. You can do very cool stuff with rotaries for example.

https://www.youtube.com/watch?v=Hr9Oi1jc4wg
 
Gamma seem to have really messed up the default X55 settings in controls, I don't quite know why.
seemed ok as it was to me, time to start messing about again.
oh well.
 
Are all the key commands on the HOTAS necessary taking into consideration using Voice Attack?

A lot of commands, as shown in the reference card, are things I am already handling through voice attack.

E.g. ship lights, targetting highest threat, activating the frameshift, changing power settings, toggling the landing gear and cargo scoop et.c.

Seems to me that Voice Attack would free up quite a few buttons for other actions... not sure what those actions or commands would be though...
 
Are all the key commands on the HOTAS necessary taking into consideration using Voice Attack?

A lot of commands, as shown in the reference card, are things I am already handling through voice attack.

E.g. ship lights, targetting highest threat, activating the frameshift, changing power settings, toggling the landing gear and cargo scoop et.c.

Seems to me that Voice Attack would free up quite a few buttons for other actions... not sure what those actions or commands would be though...

Depends. I have some voice commands, but I have the same commands mapped to the HOTAS because I do not always like to talk to myself. In fact, some things I have mapped three times since I'm using Roccat Power-Grid app on a tablet. Just for options and variation.
 
Thanks for taking the trouble to explain.
repped

You're welcome and thank you. Note that Gamma 2.0 has introduced a 'Back' option in a lot of the UI panels, which may mean the above is inaccurate.

- - - - - Additional Content Posted / Auto Merge - - - - -

Gamma seem to have really messed up the default X55 settings in controls, I don't quite know why.
seemed ok as it was to me, time to start messing about again.
oh well.

I had amended from the default and was using therefore Custom.binds. This seems unaffected by Gamma 2.0. Perhaps they have introduced some new binds in the new default?
 
Last edited:
My x55 arrived yesterday. I ordered the thing semi-hesitantly with comments out there regarding quality issues, etc. I enjoyed using my very old (but in perfect shape) MS sidewinder force feedback 2 stick + keyboard. I just wanted a better throttle and more buttons. Plus it feels nice to not use the keyboard.

My thoughts.. its construction is just fine. It is high quality, but it certainly isn't industral strength. Its a darn game stick. It feels great to fly with. If you need a good stick combo, its worth it. Don't do what I did when swapping out the spring the first time before use. BOING! the retaining ring flew up into the air and landed somewhere in the room. My new stick in hand, and I can't even use it. 40 minutes of searching, and I finally found the part under my desk behind the computer. LOL

The throttle 'thumb mouse' thing (that little black mouse ) is darn quirky, effectively useless. I'd much rather have had a third gray button. All other buttons and switches seem plenty high enough quality. I can live with it just fine. Plenty of other buttons, switches, etc.

I set up using VoiceAttack with the HCS (1.6.1) pack, and the included x55 profile. It works well.. but I'm wondering if there is a better button arrangement. Rather than reinvent the wheel, I'd rather check out what others use and emulate the config from there.

I'm open to suggestions.. i'll pour back through this thread, hopefully I can find and settle on an arrangement that I like.
 
Back
Top Bottom