Raven434th

It was never a problem until the last patch...they messed something up...also note I can kill all the other infantry standing around him no problem!

BUMP....how about some acknowledgement on this ED

Blackshark insurgent mission I cannot kill the manpad (igla) insurgent near the town...he just won't die even after unloading an entire HE and armor AP belt on him...whats up with that???:mad:

Hmm...well that seems to support a USB 2.0 port issue

my 3 desktop comps are all msi..laptop is acer...I tested on 2 of my desktops and the laptop, so its not an msi issue...unless its an msi AND acer issue??...but I think not. All are usb2.0 though and AMD chipsets.

In my case I kept both as I believe they will eventually fix it, and I have a workaround for DCS which is what I bought the hotas for...But I did have the option to return it for refund...I choose to wait it out.

People having this issue should also know there's a workaround. If you make a shifted button on the joystick to apply to all the throttle buttons, it solves the problem as its not a direct button command but "2" button commands if ya follow my meaning? example...G for gear on the throttle for a switch will give you a ghost press when in flight. Change it to say pinky button(on the joystick) plus sw1 button on the throttle and presto , no ghosting for the gear.This doesn't apply to the joystick, only commands for the throttle. Why this is, I got no idea, but it works. We shouldn't have to do it this way though, as it means we can't use the profiler directly.It also means double button commands for all programmed buttons for the throttle...pain in the ass. This is all done in the dcs editor btw not the x55 software program. So in short...ALL my throttle commands are double programmed to a button press on my joystick... button x on joystick plus button x on throttle = command = zero ghosting lots of edits to this post so it should be ok now

In my case it isn't fixed, and yes I spoke to then directly and explained the issues posted here. Its not been confirmed its an AMD issue ,but there's something of a common denominator here with 90% of the people with this problem having AMD chipsets. Best thing to do is call them directly to put a fire under there butts and get them to acknowledge that there's and issue with either their drivers or their software(I'm betting its the driver, but that's just my hunch) and to be more clear, IMO,its probably an issue/conflict between their drivers and USB2...interestingly enough...I also have the x45 and NO issues with it for a decade.ALSO whats interesting is that fix posted way back regarding the broken line thing...worked...for about an hour....So its gotta be software IMO.

A replacement won't solve the problem...I had two x-55 do the same thing (ghost presses ) on 3 different machines...All AMD btw. What I suggest is you all call tech support and report over the phone to the following people(they are fully aware of this issue),maybe then madcatz/Saitek will get off their asses and fix this. make sure you call during the day in order to get ahold of them(California time) Raymond Ruiz rruiz@madcatz.com or Victor Milian phone toll free at: 1 (800) 659-2287 BTW I have the same processor as you big10

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

Well I'll be a @#^$%$^...worked like a charm Jamey...thanks a bunch...did you report this to madcatz?

Not anymore it seems...no lights here

How do we tell if our jamers are turned on in the su25t??:cry:

Mig-29 hud info is really really small...is this what was meant in the changelog???..."Russian fighters. The angular size of HUD indication was reduced to real volumes." If so this really sucks as its very difficult to read unless zoomed into hud.Also the radar cursor is a lot bigger because of it ,like it didn't get scaled down properly.

I have msi boards on 3 comps and my labtop is acer, I only checked the hotas's on 2 msi systems and the laptop and all 3 had the same issues. All screws accounted for btw.

Ok...I just spoke with madcatz tech support in L.A California and we've been trying to pin down this issue for weeks now.I directed them to this thread so they are now aware of this ghosting issue being more than a single incident.I sent back both x-55's today for refund until they can establish if its a software issue or hardware conflict.There are 3 possibilities IMO that could be the culprit. 1.Packageing.when my rhinos showed up they were a box in a box ,no shock absorbing material at all except what was contained in the rhino box itself.Being in canada and knowing how things get banged up (temp being a factor as well)...this may or may not have been the cause. 2.hardware batch.plain and simple it could be that we simply got unlucky.Bad batches. 3. It's a driver issue with AMD chipsets.Unlikely maybe, but possible I guess given my case and the fact that others have this same issue on amd machines. Here is the number for madcatz tech support 1 (800) 659-2287 ,ask for Raymond or Victor who were handling the case for me and they should be able to glean enough info from others to maybe get these issues fixed.

Good find...setting the TS too "keyboard and mouse" worked for me in addressing issue no.1. Thanks for the solution.

Saw this at simhq posted by woofiedog: Trying to pin down some issues with the rhino, could people please post any issues you have with the X-55 as well as your system specs. some issues I've noticed so far: 1. Multiple button presses being fired when running TeamSpeak 3(confirmed by mad catz tech support).To replicate this just run TS and open the test page and press a programmed button. The joy button must be programmed with a key press 2. Ghost button presses...this occurs when sliding the throttle back and forth and causes random button presses. This can be observed in the programming window without programmed buttons.It may take a few tries of sliding the throttle at varying speeds to see this issue. I've tried this on 3 different computers with 2 different rhinos and get the ghosting to different degrees. The only thing I can see in common in my case is AMD cpu chip sets on windows 7 64 bit.

You might also want to return to the SimHQ review as some interesting dev issues have been brought to our attention.

yes ,I've seen this issue as well

In 1.2.7 will we be able to alt j into other aircraft and have a working radar??

I've noticed this as well...its not that its slow in a performance sense...but it feels that the black shark is flying through "mud" rather than air.The sense of speed has dropped compared to the previous version.I first noticed it when flying the MI-8. Anyone else notice this?

I think its a two way street

Cool saved me a 10 gig headache:thumbup:.This issue needs to be sticky somewhere

Are the sales keys merged as of today? ie can I install via ED the module and use the steam key???