Ghosting issue revisited, and my workaround

[SLangner]

First off, I finally learned where Kolbe’s BMS v1.6 keyfiles were located and incorporated his ‘minimum’ keyfile into my user profile. Like many others, I really like how he grouped various functions by location or type. This, plus his keyfiles manual, made it easier for me to get around my particular ghosting issue, make edits, and even insert a key-bind command in the keyfile.

Regarding editing, Kolbe is German, to whom English is an additional language. He made a few very minor errors that I corrected, confusing the words ‘brake’ and ‘break’ in his references to the parking brake and speed brake. Correction was simple and safe as far as key binding was concerned. I cheerfully accept being described as ‘obsessive-compulsive’ where using correct words is concerned.

I modified his ‘min’ keyfile because he did not include a key-binding command to put the radar into standby (override), at least not that I could see. I found the appropriate command in BMS’ “keystrokes” file and pasted it in his ‘min’ file. Nine years of “nose cold” calls when refueling fighters compelled me to do this.

Ghosting - AARRGGHH!! I did considerable research into the issue, and I’m certain that there is an undefined problem with the X-55 Rhino system. None of the workarounds I found in my research solved the problem. I eliminated TeamSpeak first, because it’s been a long time since I’ve flown online. I then purchased a powered USB hub and plugged the entire X-55 package into it first, then my hybrid (X-55 joystick, X-65F throttle quadrant) into it. No such luck. I also eliminated TrackIR as a potential problem.

While in the Setup|Controllers page of the UI (with my hybrid system plugged in), I often see a flicker in the bar graph of the throttle setting, and at the same time, the text display in the lower right corner of the screen shows that button 143 was activated, pressed, whatever. The trouble is, there is NO button 143. Thanks to Kolbe’s manual, I know that my hybrid configuration’s actual highest button number is 142.

Solution - After completing DX programming in the UI, I exited BMS and opened the keyfile in Notepad. I then searched for ‘142.’ The UI’s button counters start at 1, but the keyfile counter starts at 0. If I found a line in the DX portion of the keyfile defining an action for button 142, I deleted it.

I hope this helps for those of you who are also using Saitek’s X-55 Rhino hardware.

[Devious]

I fixed the ghosting by updating my chipset and USB 3.0