X55 Rhino Button Layout with Reference Card
- Thread starter Sandcracka
- Start date
You are mot alone in your hunt for the missing part..
I must have a much smaller room though as it only took just over 5 mins to find, but that was some time ago and all is well with the X55
At DRY411S,
so noted and thanks, I had changed very little but still custom, only little things seem changed such as using fire also to answer incoming coms and actually seems one or two pre set's don't work, need to rebind.
Not to big an issue and tbh im looking at some of these Customs that have been posted, might be an option so thanks to those very kind guys.
so noted and thanks, I had changed very little but still custom, only little things seem changed such as using fire also to answer incoming coms and actually seems one or two pre set's don't work, need to rebind.
Not to big an issue and tbh im looking at some of these Customs that have been posted, might be an option so thanks to those very kind guys.
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.
Having tested the above, using the mouse-nub for a single button regardless of which way you push it seems to be the way to go. Works great for triggering Boost, although I might also try it as a toggle for reverse thrust.
I tried the juke macro idea, and while it triggers properly, a second of thrusting doesn't do much, and I'm hesitant to set a 10 or 15 second macro.
I did it using the Saitek software, because I'm also running VoiceAttack (in preparation for future use with an Oculus). If you program the stick in-game, then you can easily map commands to "joystick button 42" or some such, but I haven't found a way for VoiceAttack to send joystick commands. Instead, I've mapped every command to the keyboard, then set the Saitek software to simply send the corresponding key. That way, I can have a physical button for Boost (for example) as well as also being able to say "Boost" in the microphone and have it trigger. Programming the stick took maybe 10 minutes in the Saitek software.
It also lets you program the mousenub to send keys, as mentioned above.
Well don't forget that there are two columns in the E
custom bindings set up so you can assign a joystick trigger/button/switch/dial AND a keyboard press in the game settings and therefore junk the HUD software completely, if you are so inclined.I found it difficult to get the Saitek software to play nicely with E
. Do you use an E custom bindings that is only key presses and then configure the HUD software to generate those key presses? Are there any analogue joystick/throttle settings that you are binding to ED or are you linking them all via (digital) keypresses?I'd like to use the HUD software and the Mode switch on the throttle, which ED does not recognise. I'm thinking that I'd like different modes depending on whether I'm in or out of station for example, though it is possible to do that already in a limited fashion without the Mode option. MAybe a mining mode, exploring/trading mode, and a fighting mode. Haven't quite thought it through, but yeah, that's what I'm thinking.
Do you use an E
Yes to both - everything that's digital is mapped to a key press and the Saitek software is configured to have each joystick button = the corresponding key press. And in E
(I love that that turns into an emoji), the analogue axes are mapped appropriately - pitch is mapped to joystick y axis, roll is x axis, throttle is the throttle x axis, the thruster vertical and lateral axes are the top and bottom analog thumb dials on the throttle, etc.Yep, thinking something quite similar for the modes, maybe remapping the stick for controlling the galactic map or station UI. Can't try those yet since I only have access to the tutorial.
Thanks for clarifying.
FWIW, I have the castle hat bound to the UI 'sub panels' with the fire button the select. I use the Bottom Hat H4 on the throttle to select the Target Panel (Up) the System Panel (Down) and the main panel tabs (Left and Right). The other 2 panels (radar and Comms) are assigned to TGL2.
I'm thinking it might be good to have a 'text' mode too with lots of switches and toggles sending preset messages to the comms window. Not sure whether the comms panel accepts key presses that way though, not tried it yet.
Last edited:
I'm using a TrackIR for looking at the panels, so have the bottom hat H4 controlling thrusters digitally. I find it's easier to hit that in combat than to use the analog dials, and I've got enough buttons to play with that I don't mind having them everywhere (I'm also using the POV hat on the stick for thrusters.
)Been thinking about that too. I've noticed people putting "jettison all cargo" on a toggle, and that'd freak me out. Particularly if the goal is to eventually use an Oculus and not be able to see which toggle my fingers are on. Even being able to see them, having a command that you want to use frequently (like, say, toggle cargo scoop) with a command you almost never, ever want to use on the same switch, with the possibility of accidentally triggering on a bounce would be scary.
But yeah, a "follow me" or "incoming" quick message on a toggle would work well.
Found any uses for the two rotaries on the throttle?
I'm using a TrackIR for looking at the panels, so have the bottom hat H4 controlling thrusters digitally. I find it's easier to hit that in combat than to use the analog dials, and I've got enough buttons to play with that I don't mind having them everywhere (I'm also using the POV hat on the stick for thrusters.
Been thinking about that too. I've noticed people putting "jettison all cargo" on a toggle, and that'd freak me out. Particularly if the goal is to eventually use an Oculus and not be able to see which toggle my fingers are on. Even being able to see them, having a command that you want to use frequently (like, say, toggle cargo scoop) with a command you almost never, ever want to use on the same switch, with the possibility of accidentally triggering on a bounce would be scary.
But yeah, a "follow me" or "incoming" quick message on a toggle would work well.
Found any uses for the two rotaries on the throttle?
My TrackIR arrives today
Still not sure how I will navigate the panels. I use the top hat H3 for thrusters. I must put u my most recent settings on Google Drive to share them for what they are worth.There are 5 rotaries on the throttle! I use only the 'Pinky spin' for sensor range changes.
>Been thinking about that too. I've noticed people putting "jettison all cargo" on a toggle, and that'd freak me out. Particularly if the goal is to eventually use an Oculus and not be able to see which toggle my fingers are on.
IMHO this is another big problem with the Oculus, you need to see your hands to run a complicated game like this (not to mention the seasickness and goofy thingy hanging on your face, my wife already bxxxxxx about the headphones But as for X55, it is AWESOME and I do not use that word lightly. The standard mapping in the Pilot Manual is a good starting point that can be easily customized with the ED setup (best I have seen). There are personal differences of course, like I prefer x & y on screen to map to x & y on stick with z being rotary (guess you Brits work on a different plane than us Yanks But as an example of the depth of this game, I actually ran out of axis', buttons, and dials, wanting just a couple more.
IMHO this is another big problem with the Oculus, you need to see your hands to run a complicated game like this (not to mention the seasickness and goofy thingy hanging on your face, my wife already bxxxxxx about the headphones
But as for X55, it is AWESOME and I do not use that word lightly. The standard mapping in the Pilot Manual is a good starting point that can be easily customized with the ED setup (best I have seen). There are personal differences of course, like I prefer x & y on screen to map to x & y on stick with z being rotary (guess you Brits work on a different plane than us Yanks But as an example of the depth of this game, I actually ran out of axis', buttons, and dials, wanting just a couple more.
I've put mine on the furthest toggle which is hard to reach, with silent running. These are the 2 I don't want to use unless I absolutely need to.
Thanks! Here's my setup (also attached: View attachment 2541). I think RTY3 and 4 are inversed, as mentioned in my message.
A few notes on my setup that doesn't show up (not jgm's fault):
- The mouse nipple is useless, however H4 (next to it) does a decent job if you really need a mouse cursor. So I used Saitek's tools to set that up.
- Galaxy map navigation was vastly improved for me in the Oculus using the POV hat and the witch hat on the joystick (so I have 6DOF with these two hats)
- The rotary dials set for thrust are really useful in a fight to randomly assign drift to the craft (and hence increase difficulty to get hit). Also can be used for fine tuning positioning. They have about 33% deadzone and a "stop" in the center. Unfortunately the throttle does not... (see below)
- My throttle is set as continuous (push forward, pull reverse) with about 25% deadzone. This is really useful for flipping around using FAoff/reverse in a fight, but is tricky for landing (thinking of setting some landing overrides)
- I have redundant controls for some stuff depending on what I am doing, and just because I can
- I have the bottom push button on the throttle (G3) set for Ventrilo
I have updated my Custom.binds (attached: View attachment 5061). I've gone back to the reverse button key with the slider (set using Caps Lock in the Saitek profile)
Do you have this as a blank template? I would be enormously grateful!
Templates, empty -> https://www.dropbox.com/sh/dn0n1f9bnpda0as/AAAztVIOqTAH2bcw8PaYBNJMa?dl=0