X-55 Rhino Hotas Issues and Problems

How can these companies, TM and Saitek, fail to create something that is solid and stable?

What kind of quality control is in their manufacturer process?

I was really hoping to get this HOTAS but again, it's just sounding like a big risk. Kinda stuck with what to go with now. Guess I'll go and buy an X52 Pro again in order to get back in to DCS.

Still having issues, but they do not occur as often. I am going to map my both my throttles to Rotary 4, and disable the throttles in the Madcatz software with the lock buttons for now, and see what happens while waiting for a solution from Madcatz. At least it is flyable this way,and you get full use of all the switches.

Meanwhile, Amazon has them in stock again, and I ordered a replacement. I will have both Hotas's until I have to send one back in early June.

How can these companies, TM and Saitek, fail to create something that is solid and stable?

 

What kind of quality control is in their manufacturer process?

 

I was really hoping to get this HOTAS but again, it's just sounding like a big risk. Kinda stuck with what to go with now. Guess I'll go and buy an X52 Pro again in order to get back in to DCS.

Keep in mind that in this thread you only hear of the bad stories. How many success stories do you think there are?

I've had zero issues that have blocked me from anything, there are little quirks as with anything, but honestly, its been fine with everything I fly.

Im guessing you have intel chipset, right?

mine is back too ghosting now as well:(:mad::doh:

Still having issues, but they do not occur as often. I am going to map my both my throttles to Rotary 4, and disable the throttles in the Madcatz software with the lock buttons for now, and see what happens while waiting for a solution from Madcatz. At least it is flyable this way,and you get full use of all the switches.

Meanwhile, Amazon has them in stock again, and I ordered a replacement. I will have both Hotas's until I have to send one back in early June.

It was in stock today? I am signed up for notifications if it comes back in and I didn't get anything, now it's gone again.

Yes, it was in stock yesterday morning. I signed up for a notification also, but never got it. You just have to keep checking.

mine is back too ghosting now as well:(:mad::doh:

One thing I did do this morning that may have helped, is when the ghosting starts, pause the game, move the throttle levers back and forth several times full throw, and resume. I turned my LED's all the way down as well. Something has to be going on inside that throttle mechanism.

So... i tested what Jamey says about changing the profiles... no joy. Both the profiles have jagged lines for me....

I've noticed that this is starting to happen also when i use H2 as a target designator.

Received a replacement X55 today.....Same issue.

I'm almost willing to live with it since it is much superior to the X52 non pro I have been using, just wish Madcatz would respond with some support

People experiencing the ghost button issue, are you running a wireless network card? I'm thinking maybe some type of interference. Just disabled mine for diagnostic purposes

Edit, that didn't help

I´ve just received my new X-55 and i´m very happy with it. By now no issues, no ghost buttons, no flaws.

But i have a question. I came from a X-45, an in that joy the mouse axis in the throttle could be configured like buttons in a 8 or 4 way. In my A-10C profile i used this mouse as buttons for slew and was very accurated.

Now in the X-55 the mouse axis can´t be assigned as buttons, only with bands it could be reproduced a similar slew movement but by far it´s a lot less accurated.

Anyone knows how to use the mouse axis as the slew for the A-10C with more precision and accurated movement?

Thanks.

Anyone have the X-55 working on Windows 8.1? I installed over a previous X-52 (not pro) installation, and can't get the MadCatz H.U.D. to recognize the joystick (it sees the throttle). the OS sees the joystick (somewhat) and it appears to work in DCS. I just can't configure it, nor get the profiler to work properly.

I opened a ticket on the Mad Catz site, but they have been ignoring me.

Anyone have the X-55 working on Windows 8.1? I installed over a previous X-52 (not pro) installation, and can't get the MadCatz H.U.D. to recognize the joystick (it sees the throttle). the OS sees the joystick (somewhat) and it appears to work in DCS. I just can't configure it, nor get the profiler to work properly.

 

I opened a ticket on the Mad Catz site, but they have been ignoring me.

Hi!

Im new at dcs and I have just purchased the x55.. Seeing the exact same problem as described above.

After installation, it worked perfect, loading profiles, worked in dcs. After a reboot, the MadCatz software all of a sudden doesnt respond/recongnize the stick in the calibration window.

But it works were you assign the buttons etc and works in the game. But no profile can be loaded.

Win 8.1 on intel i5 and asus motherboard.. have tried changing usbports and installing/uninstalling the stuff.. no change. :(

Re: X55 and Windows 8.1

http://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

Looks like MadCatz is aware of the issue and working on it. Past that, I don't have much of an update.

Okay, I made some progress.

I uninstalled all drivers and software, then re-installed everything.

I get two identical icons in the tray. One is for the throttle and the other for joystick. There is no way to tell them apart. Best I can tell, you need to load two different profiles. I'll have to experiment with that. Clicking on one will launch the HUD, and you can calibrate the throttle. Clicking on the other allows you to work on the joystick.

Either one allows you to program both devices. but I"m not sure if what you create applies to both of them or not.

I love the device, but the software needs improvement.

A friend of mine just pointed me to this thread...

I have had 4 Support Tickets in with Saitek Support starting last February!! They were all about programming with the HUD and driver issues that would send repeating keypresses when I just pressed a button once or if I held the button down. They NEVER asked me even once if I used TEAMSPEAK! I used to have my x52 pro plugged into a USB Hub for years. And they never asked me where I had the x55 plugged in either. As a matter of fact, they had absolutely no 'Standard Procedure' or script that they followed to find out important information. They were totally useless...

Thanks for documenting the solution to this TS bug here. My x55 Rhino seems to actually be working after 4 months of driving me crazy!! I love the stick, but I hate the company. They are complete morons.

PS: If you have problems with your x55 Rhino, also don't use a USB HUB. Mine caused delayed commands to be sent about 30 seconds later.

I just got my X-55 today. I installed the drivers, but not the HUD software. DCS recognizes the HOTAS perfectly, it calibrates dead center, and all buttons are immediately responsive.

It might be because I have one of the newer batches directly from Saitek and they've fixed some of the issues, but if you're only using the HOTAS with DCS, I highly recommend NOT installing the HUD software. Install the drivers only.

Has anyone taken it apart to do modification on the twist axis spring tension? I've seen everything there is to see about the base spring- but has anyone taken it one step further?

Hey everyone, I signed up to this site to try and provide you with a possible solution to your ghost key presses with the X55 throttle.

I had the same issues and to resolve it I installed the USB3 drivers from my motherboard provider as well as a tweak in the PC bios. The thing I think fixed it was disabling Legacy USB Support in said bios. Since doing that all the issues have stopped and the unit has been pretty fantastic.

Hope this helps you as I couldn't find a solution online but hopefully this is a universal fix for everyone with the problem!

Need to be careful with disabling Legacy USB Support on some motherboards, it will cause the bios to not recognize your usb keyboard and mouse.

You won't be able to get back into the bios during booting without a PS2 keyboard or resetting the bios defaults.

Need to be careful with disabling Legacy USB Support on some motherboards, it will cause the bios to not recognize your usb keyboard and mouse.

You won't be able to get back into the bios during booting without a PS2 keyboard or resetting the bios defaults.

As far as I know it shouldn't effect that many people in this day in age if any since most chipsets now support USB on bootup and Legacy support is just for USB 1.0 devices. Go back to pre 2003ish and you may have a problem but doubt anyone playing this sim will have such and old piece of hardware.

Would just advise anyone trying it to know how to reset the bios to defaults before they disable Legacy to be on the safe side. Or to start with ensuring their USB3.0 drivers are installed correctly from their manufacturer as I did.

Yea, I guess I worded it a little wrong, should have said it may cause the bios to not recognize the devices.