Hardware & Technical Saitek x55 rhino
- Thread starter Oculus
- Start date
Hi there!
I received my X-55 throttle a few days ago, and even if it's made of cheap plastics and poor microswitches, it's a great tool full of buttons.
No particular issue so far.
I'm using the throttle with a Logitech Extreme 3D pro (+head tracking)
Here's the current bindings :
I created that reference sheet for my tablet as I only wanted the throttle on screen.
I also managed to use the mouse nipple as an additional 4-way hat, using the 'bands' configuration (three bands per axis - one for the deadzone). The feeling of the tiny thing isn't great but still useful for non-essential functions (tests in progress)
The rotary 4 now controls my music player volume (Foobar2000).
Tweaking, tweaking, tweaking…
I received my X-55 throttle a few days ago, and even if it's made of cheap plastics and poor microswitches, it's a great tool full of buttons.
No particular issue so far.
I'm using the throttle with a Logitech Extreme 3D pro (+head tracking)
Here's the current bindings :
I created that reference sheet for my tablet as I only wanted the throttle on screen.
I also managed to use the mouse nipple as an additional 4-way hat, using the 'bands' configuration (three bands per axis - one for the deadzone). The feeling of the tiny thing isn't great but still useful for non-essential functions (tests in progress)
The rotary 4 now controls my music player volume (Foobar2000).
Tweaking, tweaking, tweaking…
Last edited:
Great stuff Bourrinopathe.
Would you mind sharing how you configured the rotaries (the top and bottom ones on the right and your "scanner range" one)?
I've had trouble getting them to work and I think it's just my lack of familiarity with the Saitek software. I've been trying to get scanner range on the top rotary for ages!
Would you mind sharing how you configured the rotaries (the top and bottom ones on the right and your "scanner range" one)?
I've had trouble getting them to work and I think it's just my lack of familiarity with the Saitek software. I've been trying to get scanner range on the top rotary for ages!
I use H3 hat switch for panels, H2 for navigating them and H1 left / right for prev / next tab. H4 is for thrusters up / down / left / right.
It's nice that there are enough buttons for each operation.
Thanks.
I have no idea what I could bind to the top and bottom rotaries
Right now, they are just two big buttons (FAOff and Reverse thrust / Shield Cell).
The 'scanner range/zoom' has been directly assigned using the game controls options. Just roll the rotary to bind it (I kept the 'Fall Back' option in the Saitek programming tool). It acts like an input repeater for each direction. I didn't find any better use for it.
I think I'll have search the thread for some ideas
I have no idea what I could bind to the top and bottom rotaries
Right now, they are just two big buttons (FAOff and Reverse thrust / Shield Cell).The 'scanner range/zoom' has been directly assigned using the game controls options. Just roll the rotary to bind it (I kept the 'Fall Back' option in the Saitek programming tool). It acts like an input repeater for each direction. I didn't find any better use for it.
I think I'll have search the thread for some ideas
After my previous post I think it's fair from me to say, I bought a powered USB hub to plug the X-55 in and the ghosting issue on the throttle disappeared. Now it's a couple of days I'm playing without problems and I'm quite happy with my new controls. So thank you especially to Neillm and Skyflyer who put me in the right direction
I really like the throttle, it's awesome, the action is as smooth as I could ask. The stick is good quality but less impressive, I settled for the yellow spring, but I really like the quality of the hats. Also the default bindings for the X-55 aren't half bad, I just changed a couple of buttons and everything else was where I wanted it already.
I really like the throttle, it's awesome, the action is as smooth as I could ask. The stick is good quality but less impressive, I settled for the yellow spring, but I really like the quality of the hats. Also the default bindings for the X-55 aren't half bad, I just changed a couple of buttons and everything else was where I wanted it already.
The 'scanner range/zoom' has been directly assigned using the game controls options. Just roll the rotary to bind it (I kept the 'Fall Back' option in the Saitek programming tool). It acts like an input repeater for each direction. I didn't find any better use for it.
I think I'll have search the thread for some ideas
Aha, thanks very much. Got it sorted now!
Heyas,
So I got the hub today.
Just played for about an hour and a half without any problems whatsoever.
Looks like a fix
Thanks for all of your replies. I just hope that any other people looking to buy an X-55 know about this before hand, and have a hub ready to go, otherwise it could be a really offputting experience for them.
So far, I am enjoying the X-55. It's a nice stick, and the throttle feels great. Plenty of buttons to manage most of what the game has to throw at us.
I would still recommend having a keyboard & mouse handy though. But overall, it's looking like a pretty good experience so far.
Thanks again for the help, and I'll be seeing you all out there in the great voids
Peace.
So I got the hub today.
Just played for about an hour and a half without any problems whatsoever.
Looks like a fix
Thanks for all of your replies. I just hope that any other people looking to buy an X-55 know about this before hand, and have a hub ready to go, otherwise it could be a really offputting experience for them.
So far, I am enjoying the X-55. It's a nice stick, and the throttle feels great. Plenty of buttons to manage most of what the game has to throw at us.
I would still recommend having a keyboard & mouse handy though. But overall, it's looking like a pretty good experience so far.
Thanks again for the help, and I'll be seeing you all out there in the great voids
Peace.
How to automate Docking and other Stuff
I wanted to automate the tedious "request docking" sequence (1 e e Space s Space q q 1), but it did not work, after I figured out what was missing.
first you must make sure that the in-game option include keyboard strokes:
now can program a macro for your chosen button, here TGL 4 Up:
type in the key sequence
1 e e space s space q q 1
left click in the macro so all keys have a blue frame::
right click and select "set Delay"
Then input 0,1 secs, otherwise the simulated keystrokes are too fast
*With beta 2.05 I had to set the first delay to 0.2 secs in order for the macro to work.
confirm the newly created macro and leave edit mode by clicking the green checkmark:
save the profile
test it
and important!!!
aktivate the profile!! (this was the missing bit) with a click on the blue target cross:
for a further test open an editor of your choice
when you have done everything right, the Saitek software should emulate the keystrokes:
and then it should also work in the game!l
You can also set a name to your macro, so you can easily assign it to another button:
I hope this small tutorial is of help for all Saitek users.
Cheers
Dan Generous
I wanted to automate the tedious "request docking" sequence (1 e e Space s Space q q 1), but it did not work, after I figured out what was missing.
first you must make sure that the in-game option include keyboard strokes:
now can program a macro for your chosen button, here TGL 4 Up:
type in the key sequence
1 e e space s space q q 1
left click in the macro so all keys have a blue frame::
right click and select "set Delay"
Then input 0,1 secs, otherwise the simulated keystrokes are too fast
*With beta 2.05 I had to set the first delay to 0.2 secs in order for the macro to work.
confirm the newly created macro and leave edit mode by clicking the green checkmark:
save the profile
test it
and important!!!
aktivate the profile!! (this was the missing bit) with a click on the blue target cross:
for a further test open an editor of your choice
when you have done everything right, the Saitek software should emulate the keystrokes:
and then it should also work in the game!l
You can also set a name to your macro, so you can easily assign it to another button:
I hope this small tutorial is of help for all Saitek users.
Cheers
Dan Generous
Last edited:
Vlodec
Banned
Very nice, I use something similar with VoiceAttack. But the problem with these macros is that they depend on the cursor being in the right place to begin with. What's required is a hot key. In fact I'd suggest that every line in every panel should be bindable. (Yes I know it's impractical if you only use a keyboard but for the growing number of VoiceAttack users multiple key combinations are not a problem.)
This is true, it worked well for me in Beta 1 trading, but I noticed in beta 2 once I was running missions it would often cancel missions then attempt to dock.
Rhino works a treat
My brand new Rhino arrived today and I installed it on my 8.1 system. Had a little trouble with the drivers until I spoke to Mad Catz on the phone who told me to install them and the software with both devices unplugged. No problem after that.
Also observed an issue with the stick & throttle backlights working intermittently. I had them plugged into a USB 2.0 unpowered hub. Mad Catz advised using USB 2.0 slots connected directly to the motherboard or a powered hub. I chose the first and have had no issue since thru 5 hours of continuous use.
Now all I need to do is figure out a better control map as the ED preset sucks!
My brand new Rhino arrived today and I installed it on my 8.1 system. Had a little trouble with the drivers until I spoke to Mad Catz on the phone who told me to install them and the software with both devices unplugged. No problem after that.
Also observed an issue with the stick & throttle backlights working intermittently. I had them plugged into a USB 2.0 unpowered hub. Mad Catz advised using USB 2.0 slots connected directly to the motherboard or a powered hub. I chose the first and have had no issue since thru 5 hours of continuous use.
Now all I need to do is figure out a better control map as the ED preset sucks!
I found the opposite - I always had this issue with either USB3 ports, or plugged into USB2 ports not directly on the motherboard. Once I did that problem was solved.
Hi there!
I received my X-55 throttle a few days ago, and even if it's made of cheap plastics and poor microswitches, it's a great tool full of buttons.
No particular issue so far.
I'm using the throttle with a Logitech Extreme 3D pro (+head tracking)
Here's the current bindings :
I created that reference sheet for my tablet as I only wanted the throttle on screen.
I also managed to use the mouse nipple as an additional 4-way hat, using the 'bands' configuration (three bands per axis - one for the deadzone). The feeling of the tiny thing isn't great but still useful for non-essential functions (tests in progress)
The rotary 4 now controls my music player volume (Foobar2000).
Tweaking, tweaking, tweaking…
Can I ask what you used to make this?
Part of the problem is that the menu opening sequence became slower for some reason in B2 so it doesn't actually get to the second tab right command of your macro and instead cancels a mission...had exactly the same thing. I had to adjust the macros I use on both the Logitech G13 and the X55 to include around 750ms delay between the "UI Panel 1" command and the first "tab right" command to make it work.
You can edit the X55 profile save (.pr0 file) directly. The part in question should look something like this...the 2EE is hex for 750ms delay before the first tab right executes:
[actioncommand=a8f7717a-33f8-470e-9e85-1533202d79bb name='Docking Request'
[actionblock=macro
[action device=keyboard usage=0x0000001E page=0x00000007 value=0x00000001]
[action device=keyboard time=0x00000032 usage=0x0000001E page=0x00000007]
[action device=keyboard time=0x000002EE usage=0x00000061 page=0x00000007 value=0x00000001]
[action device=keyboard time=0x00000032 usage=0x00000061 page=0x00000007]
The [action device=keyboard] statements are in pairs...a key down and key up. So this is saying
- press the 1E key (1 or NumPad1, can't remember which, to bring up the UI Panel)
- wait 50ms then release the 1E key
- after 750ms press the 61 key (NumPad 9 = tab right)
- wait 50ms then release the 61 key
The Saitek software editor is so appalling, compared to say the Logitech gaming software, that I found it much easier to edit the save files directly once you understand the format.
For the rest of my docking macro I used 50ms between key down and key up (time=0x00000032) and 100ms before the next key press (time=0x00000064) and it works fine, all the time now.
Profile programming problem Windows 8.1
Ah Ha! I'm having a problem with the programming software which seems similar to this (I'm on 8.1). Although the LED brightness control is working, I'm not able to activate any of the Key programming boxes by Mechanical operation of the stick/throttle and the profile and test icons are always greyed out, so it appears the devices and the software are not fully connecting together. It means I can't program any of the buttons/axes.
You say Saitek have admitted there are problems...is there a reference anywhere? I can't find a mention on their website and my ticket hasn't been answered yet
Fixed! I hadn't finished installing the drivers properly...probably an indication of how well I'm going to do at this game
Ah Ha! I'm having a problem with the programming software which seems similar to this (I'm on 8.1). Although the LED brightness control is working, I'm not able to activate any of the Key programming boxes by Mechanical operation of the stick/throttle and the profile and test icons are always greyed out, so it appears the devices and the software are not fully connecting together. It means I can't program any of the buttons/axes.
You say Saitek have admitted there are problems...is there a reference anywhere? I can't find a mention on their website and my ticket hasn't been answered yet
Fixed! I hadn't finished installing the drivers properly...probably an indication of how well I'm going to do at this game
Last edited:
Ah Ha! I'm having a problem with the programming software which seems similar to this (I'm on 8.1). Although the LED brightness control is working, I'm not able to activate any of the Key programming boxes by Mechanical operation of the stick/throttle and the profile and test icons are always greyed out, so it appears the devices and the software are not fully connecting together. It means I can't program any of the buttons/axes.
You say Saitek have admitted there are problems...is there a reference anywhere? I can't find a mention on their website and my ticket hasn't been answered yet
Hi Ray,
Here's from the X55 Faq on the Saitek Website which states they are aware of bugs in 8.1http://support.madcatz.com/Knowledgebase/Article/View/486/176/im-running-on-win81-and-when-i-go-to-the-game-controllers--settings-tab-in-the-control-panel-the-throttles-settings-say-it-needs-to-be-calibrated-whats-going-on
Although this link isn't regarding your issue, it does show they are aware of an incompatibility with 8.1 and their drivers/software
They haven't been too open regarding what bugs they are aware of and I'm betting they've got a pretty decent sized list.
What is annoying me though is there haven't been any updates to the software or drivers since launch. it's almost like they released it and now they don't care.
Hi ZZR600
Thanks for you response...its an interesting read, isn't it? It was 3 days between submitting a ticket and my discovery of my own ineptitude in failing to install the drivers properly and, apart from the automatic acknowledgement of the ticket, I've had no contact from Saitek (or Mad Catz).
It seems odd, given the size and longevity of this company, that their customer support takes so long. You would think that products costing this much would be supported better, and if indeed there are compatibility issues between software and OS's, they would be breaking their necks to get them sorted. I would certainly have returned the device for a refund had I remained unable to program it.
Anyhow, I'm a happy bunny again :smilie: and the new hot topic is deciding whether to use the mouse nipple for headlook or not...
Thanks for you response...its an interesting read, isn't it? It was 3 days between submitting a ticket and my discovery of my own ineptitude in failing to install the drivers properly and, apart from the automatic acknowledgement of the ticket, I've had no contact from Saitek (or Mad Catz).
It seems odd, given the size and longevity of this company, that their customer support takes so long. You would think that products costing this much would be supported better, and if indeed there are compatibility issues between software and OS's, they would be breaking their necks to get them sorted. I would certainly have returned the device for a refund had I remained unable to program it.
Anyhow, I'm a happy bunny again :smilie: and the new hot topic is deciding whether to use the mouse nipple for headlook or not...