X55 Rhino Button Layout with Reference Card

This is a great thread and I thank you to all those have put up their binds files and images, but annoyingly my X-55 trigger button has decided to break, so I've had to send it back. Sad times, won't be playing ED until after New Year now. :mad: :(
 
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated

Indeed, have not really played much recently, been ill, came back to do a trade left dock and went to FSD and throttled up, that took me to map ?? came out of map and what do you know im taking heat damage on silent running, used the set silent running to get shields back and hey, that move jettisoned my cargo !!!, My toggles were set just fine last time I played.
The only remedy was to leave game so I could have a look and reset, I had a similar problem back in Beta but I put it down to the beta or an update. Throttles for Map ?? I just about ready to give up.

Love the Tag > ED 209 (Put down your weapons) lol
 
Last edited:
^^^what he said

You don't need to use the saitek profiler at all unless you want to program a button to do something not provided for in the game.

I started with the X55 option under controls in the game and then changed the buttons I wanted to and it automatically saves it as a custom profile. I did however use the Saitek software to assign f9 and f12 to the pinky switch on the throttle to pause and recenter my TrackIR, as I tend to only use track IR in combat and prefer the hat switch for the consoles during normal trade runs.

Hi Scrogg. I'm also using TrackIR so I'm kind of interested in your controls setup. Would it be possible for you to share your Custom.binds file?
 
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated

Not sure why this is happening to you guys. I've never had to remap my bindings since beta.
 
Is anyone else having trouble with there X55 bindings??
When ever I start ED with previously saved bindings have gone & I have to do it all over again, which is a damn chore.
Any help on this would be appreciated

This is a complete shot in the dark here, but are you using something like EDTracker or some other tracking solution? I found that if you have this turned on and the axes mapped in the ED settings it stores the controller ID in the custom.binds file. If you then start the game up with the tracker turned off, it rejects the custom.binds file with having a unrecognised device. This then defaults back to the standard settings and you've lost all your bindings. If this happens, you should see an additional error file along custom.binds which tells you what happened.

As I say, shot in the dark, but it may help.

Thanks.
 
I found the throttle axis spinners are a poor choice for thruster control. They have a centre point, so anything other than this gives a permanent send, and therefore a constant thrust command.
 
I've just mapped buttons 25 & 27 on my X55 (the ones on the lower hat on the throttle) to Left & Right on the UI panels and they work fine, for whatever that's worth.

Wish I could be more help but I'm stumped.

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).


thanks for this, was trying to find out if this was possible & how, you've done the leg work for me :)
 
Into the 21st Century!

Thanks for the reference card. Just bought the X-55 to replace the keyboard/mouse combo. Used to play the original on the BBC Acorn & Commodore 64 but this has far too many keys for just keyboard use.

The default setup for the X-55 needed tweaking for me and this layout looks excellent. Thanks for doing the hard work for me :)

Happy flying
 
Sandcracka and I have been playing together since Feb 2010 and I am always amazed at how resourceful and helpful he is. One thing I do NOT like about Saitek is their naming scheme for buttons. Windows and every single game identifies their hardware buttons by NUMBER, but Saitek uses letters in their graphics and programming software, making it very confusing to setup if one doesn't know the button numbers by heart (there's a LOT of them with the Rhino).
 
hey guys, I set up some binds, and my lateral thrusters (up down left right etc) seem to work for about 15 minutes then fail, have the left hat switch as what i want for that, works for the take off first time in game then it just doesnt work after the next landing. going to try some different binds but i think it might be a software bug on frontiers side atm... any others with this experience?
 
In the Saitek software, you can program it to do other things than mousing, although it's super sensitive and frequently will trigger up, say, when you want to go right. I've had some success mapping one axis of it to next UI panel/previous UI panel in the user interface using the bands, with a giant (like 60%) dead zone in the middle.
Another option that might work would be to set every direction on it to the same key, again, with a large deadzone. Something like Boost or Hyperdrive where you just need another button under your thumb, but you don't really care about left vs. right or up vs. down.

And now that I think of it, you could actually do something really slick using the randomness: set each direction to a juke macro, such as "thruster up for 1 sec, thruster right 1 sec, thruster left and down 1 sec" or something, with each direction being a different order of thrusting. Then just tap the stick in any direction in combat to jink a bit if someone's shooting at you.

Nice idea! :)
 
I've revised my bindings a bit based on more experience with the game, as well as new features introduced. I've also built an EDTracker so the various ways of looking around are no longer that important to me in the X55 bindings, but even without EDTracker I found that I was never using the POV hat to look around, but only the mouse nipple. So I've changed the POV hat to be used for targeting, and moved the subsystem targeting to the lower throttle hat. (I considered using it for lateral thrusters, but it becomes problematic in a dogfight if you want to apply thrusters and shoot at the same time, hence lateral thrusters remain on the throttle hat.)

Anyhow, as before, the mouse nipple on the throttle needs to be configured to a mouse in order to be used for analogue headlook, and the slide switch on the throttle should be bound to caps lock held down when enabled, and caps lock release when sliding back. This way it can be used to toggle throttle reverse (the capslock key was chosen because it does not spam into any text boxes or trigger shortcuts, but it does toggle caps). Both bindings can be ignored without affecting other usage, e.g., EDTracker users may simply disable mouselook an ignore the mouse nipple on the throttle.

FYI, both of the linked bindings are the same, the ones that removed the look controls from the POV hat.
 
Standing on the shoulders of giants.

Thanks to those who have taken the time to post & respond to posts, upload bindings & make resources available to others (jgm, sandcracka & DRY411S particularly) :D

Attached are my bindings & Saitek .PR0 files (had to rename with additional ".txt" to enable forum upload, don't forget to remove to use) & reference sheet.


I've taken the slightly unconventional path, using the Stick D button (near the pinky switch) as a modifier & UI focus. I found I was frequently firing secondary weapons when mapped here, so I moved them to the Stick C button.
Holding button D & using the stick castle hat will access the UI panels (pretty standard) with a combination of Castle Hat & Throttle H3 Hat for navigating the menus, trigger is select, C is back.

Pinky switch is used as the primary hardpoint deploy, although the trigger & C button do this too.

As mentioned, Button D is a modifier - this has also been used to map the stick to control vertical & lateral thrusters, very useful for landing or evading incoming fire. Thrusters are also mapped to Throttle Hat H4.
This is also the method I've used for navigating the galaxy map.


Throttle E Is mapped to all stop - I am still a noob & occasionally need to slam on the anchors
Throttle H is mapped to boost (left index finger)
Throttle I is mapped to super cruise/hyper Jump (left middle finger)
Throttle Ki up/down is used for galaxy map

SW1/2 is mapped to landing gear toggle
SW3/4 is mapped to cargo scoop toggle
SW5/6 is mapped to ship lights toggle

TGL4 is currently programmed as a docking request (Up & down) using the method detailed by DRY411S with the same caveats (UI focus must be on NAVIGATION Tab (or you could abandon missions accidentally). This does not require the button to be held, just flick it.

one of the rotaries is mapped as sensor zoom, but I forget which - never use it

There are some other bits & bobs bound, but they're mostly leftovers from control experiments.


Hope this is as helpful to others as previous posts have been to me.:)


by the way, I don't have EDtracker or voiceattack, I realise they make life easier, but as my primary play location is on the sofa next the wife while she's watching tv, she doesn't do docking requests...:p


edit- I just realised that the reference sheet I've attached is missing the throttle image. it'd be easiest for you to save the bindings attached and feed them into JGM's fine reference sheet generator here: http://www.mcdee.net/elite/

that's what I get for using a MacBook pro BootCamp'd with Windows 8....
 
Last edited:
Very exciting! I just ordered my X-55 online today. Problem was I wanted it NOW! How do you solve problems? Throw money at them of course. Priority shipping and I get it Friday. So freaking stoked!

Thanks to all posters who had profiles, macros etc listed. Very cool guys! :)
 
:DCongratulations, you'll be very happy with it!
It might seem obvious, but before you start customising the default X55 bindings in ED, try them out for size first, see what does & what does not work for you as it is.
 
Back
Top Bottom