X-55 Aircraft Starts Every Mission Trimmed to the Extreme Right
-
I have my trims assigned to RTY 3 and RTY 4 on the base of the throttle. In the setup page (BMS), I then assign and calibrate both rotaries. Have you tried that option?
-
I have my trims assigned to RTY 3 and RTY 4 on the base of the throttle. In the setup page (BMS), I then assign and calibrate both rotaries. Have you tried that option?
Well, when I set these up to use the rotaries I have an entirely new problem - and that is that my rotaries seem to function now like three way switches. They are either in the middle, full to the left, or full to the right, I am not sure why. Any advice on this issue?
In the meantime, I have decided that my issue may be related to ghosting. After a near-disastrous dogfight with a Mig-29S because every time my aircraft spawned in I was having to retrim my aircraft, I installed every game under the sun that would possibly use my joystick and ran through them all to test with.
What I found was that when I was manipulating my throttle with my hands not touching anything but the base of the throttle, my aircraft or spacecraft was consistently diving down and to the right. This happened across multiple games.
Also, I don’t seem to be able to clear out a mapped setting. Is there a method for this that I missing? I wanted to try unmapping the buttons on the front of the throttle, they sometimes show up when I am using the throttle but I feel like this is an issue with my bumping them, not a ghosting issue.
EDIT: This problem is exaggerated by the fact that, for whatever reason, I cannot trim my aircraft while I am on the ground.
-
Well, when I set these up to use the rotaries I have an entirely new problem - and that is that my rotaries seem to function now like three way switches. They are either in the middle, full to the left, or full to the right, I am not sure why. Any advice on this issue?
In the meantime, I have decided that my issue may be related to ghosting. After a near-disastrous dogfight with a Mig-29S because every time my aircraft spawned in I was having to retrim my aircraft, I installed every game under the sun that would possibly use my joystick and ran through them all to test with.
What I found was that when I was manipulating my throttle with my hands not touching anything but the base of the throttle, my aircraft or spacecraft was consistently diving down and to the right. This happened across multiple games.
Also, I don’t seem to be able to clear out a mapped setting. Is there a method for this that I missing? I wanted to try unmapping the buttons on the front of the throttle, they sometimes show up when I am using the throttle but I feel like this is an issue with my bumping them, not a ghosting issue.
A powered USB hub resolved all the ghosting issues for me. Somehow, I still believe you have some ghosting. The hubs are cheap and may be an easy fix. Before I got the hub, I had to make sure I did not program any critical commands to my throttle…like gears, etc. I did not find a way to unmap the buttons. I just put commands that did not affect flight, but was still annoying. No problem at all now with the powered USB hub.
-
A powered USB hub resolved all the ghosting issues for me. Somehow, I still believe you have some ghosting. The hubs are cheap and may be an easy fix. Before I got the hub, I had to make sure I did not program any critical commands to my throttle…like gears, etc. I did not find a way to unmap the buttons. I just put commands that did not affect flight, but was still annoying. No problem at all now with the powered USB hub.
I am already running both of mine through a powered USB Hub.
-
I am already running both of mine through a powered USB Hub.
Roger that. When you set up your trims to the rotaries, are you using the Saitek software, or are you using the BMS setup page?
-
Topic title pretty much says it all. I have an X-55, and every mission I start off the aircraft starts off trimmed to the extreme right, in just a few seconds my plane is completely inverted unless I immediately correct with my stick when the mission loads in.
I tried mapping my trim commands to stick buttons and using those to trim the aircraft in, this works about 50% of the time. I tried mapping them to an adjustable knob (AKA: Axis) on the throttle and that doesn’t work at all, it’s either full left full right or centered, but with the knob set to the center if the aircraft loaded in trimmed right it continues to lean to the right even when the trim knob is set to center.
I tried calibrating my stick outside of Falcon (in Windows) and I made sure to center it (hands off the stick) using the button in Falcon. Tried restarting, tried unplugging the hardware and plugging it back in, tried updating my drivers, tried re-installing my drivers. I make sure hands are off-stick when the mission loads too. Doesn’t matter.
Any other creative ideas?
1) Did you get the latest drivers from saitek (not madcatz) page?
- X55_Rhino_7_0_33_91_x64_Software / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_33_91_x64_Software.exe
- X55_Rhino_7_0_32_81_x64_Drivers / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_32_81_x64_Drivers.exe
2) Have you properly calibrated you axes in the HUD software window [CALIBRATE AXES]?
3) After having calibrated and having moved the stick afterwards for test, does it re-center properly after the release?
IF not, your magnet holding “hat” (picture one in link below) might be shaking and throwing it off *:
https://www.benchmarksims.org/forum/showthread.php?18306-Project-X55-GERMANY-%28Mod%29&highlight=germany+modIF OK, have you centered the device (stick) in the UI of BMS itself aswell?
- This mechanical “play” of the magnet carrying “hat” is a reason, why i modded the whole thing.
-
@A.S:
1) Did you get the latest drivers from saitek (not madcatz) page?
- X55_Rhino_7_0_33_91_x64_Software / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_33_91_x64_Software.exe
- X55_Rhino_7_0_32_81_x64_Drivers / ftp://ftp.saitek.com/pub/software/full/x55_rhino/X55_Rhino_7_0_32_81_x64_Drivers.exe
I did this, no change.
@A.S:
2) Have you properly calibrated you axes in the HUD software window [CALIBRATE AXES]?
I did this too, still no change.
@A.S:
3) After having calibrated and having moved the stick afterwards for test, does it re-center properly after the release?
Yes it does, in the SAITEK software
@A.S:
IF not, your magnet holding “hat” (picture one in link below) might be shaking and throwing it off *:
https://www.benchmarksims.org/forum/showthread.php?18306-Project-X55-GERMANY-%28Mod%29&highlight=germany+modYes, I want, but shipping to Europe is expensive and I am not brave enough to try to mod it on my own. I fried an X52 (non pro, fortunately) trying to upgrade it. Electronics are not my forte. Programming, on the other hand…
@A.S:
IF OK, have you centered the device (stick) in the UI of BMS itself aswell?
Yes, moving the stick in the UI shows full range of motion. Letting it go centers it again perfectly with no problems.
@A.S:
- This mechanical “play” of the magnet carrying “hat” is a reason, why i modded the whole thing.
I hope that’s not the issue, but all I can do now is hope.
-
Well.
In desperation, I removed them from the powered hub. Last flight? Totally level. Go figure.
EDIT:
Nope, still broken on subsequent launch. This is maddening.
EDIT AGAIN:
Cannot explain - I created a NEW keystrokes file and remapped all my keys (no small feat, I assure you). Whatever was in the old keystrokes file was breaking it. If I load it back up, problem comes back. Switch keystrokes file again? Problem resolved. Go figure.
-
Very wicked….from hardware point of view and from test screens it seems your stick is 100% fine.
-
Can you connect them directly to your PC rather than using the USB hub? I found that issue with other joysticks. My USB hub was not providing the signals correctly.
-
EDIT AGAIN:
Cannot explain - I created a NEW keystrokes file and remapped all my keys (no small feat, I assure you). Whatever was in the old keystrokes file was breaking it. If I load it back up, problem comes back. Switch keystrokes file again? Problem resolved. Go figure.
Well, that simply “smells” like input errors or conflicts in your input defintions (keystrokes). In other words your stick is fine and no warranty usage is required (which is good news).
-
Can you connect them directly to your PC rather than using the USB hub? I found that issue with other joysticks. My USB hub was not providing the signals correctly.
Yes, you can connect the X-55 directly to your PC. For some that have ghosting issues, there is an option to use the powered USB hub.
-
Yes, you can connect the X-55 directly to your PC. For some that have ghosting issues, there is an option to use the powered USB hub.
I think he was suggesting I try that (which I did: initially it seemed to work because it reset all my key-binds, but after I restarted the PC it recognized it was the same stick, restored the keybinds, and I had the trim issue again).
@A.S:
Well, that simply “smells” like input errors or conflicts in your input defintions (keystrokes). In other words your stick is fine and no warranty usage is required (which is good news).
Yes indeed, it seems to be just optimum now, except that I am using the BMS file instead of the keystrokes file and I have no idea what some of the controls are.
The thing that confuses me about this is that it seems like the keystrokes file is JUST for keybinds, I don’t understand how it relates to the stick centering, but apparently it does or I wouldn’t have had this issue.
-
Hmm… i am not using keystrokes anymore for my x55… instead BMS DirectX assignments.
-
….
The thing that confuses me about this is that it seems like the keystrokes file is JUST for keybinds, I don’t understand how it relates to the stick centering, but apparently it does or I wouldn’t have had this issue.
:hmmmm: …. that’s not necessarily correct. If there are DX assignments (i.e. direct call backs for the joystick/HOTAS) those are in the keyfile as well. Although not certain, I agree with A.S. that it was some unintended command in the keyfile, which you’ve now eliminated. I’d guess it was something commanding the roll input, not so much a stick centering issue.
@A.S:
Hmm… i am not using keystrokes anymore for my x55… instead BMS DirectX assignments.
I am convinced that this (DX) is absolutely the way to go for joystick/HOTAS programming. Unfortunately it ‘looks’ intimidating and I think people avoid it because they don’t understand it. In reality, especially if you work from Kolbe’s spreadsheet (C:\Falcon BMS 4.32\User\Joystick\Generic\Kolbe\BMS-DX-Generator 1_6.xls), it’s fairly easy to setup and use in most cases.
-
Well I have a new fun glitch for you. Today my keyboard was spazzing out (I thought) the up arrow was stuck. Like, the key was okay, but the computer seemed to think my up arrow was stuck on.
I reached over and nudged my X-55 throttle, and it stopped.
Ghosts in the machine, indeed.
-
Well I have a new fun glitch for you. Today my keyboard was spazzing out (I thought) the up arrow was stuck. Like, the key was okay, but the computer seemed to think my up arrow was stuck on.
I reached over and nudged my X-55 throttle, and it stopped.
Ghosts in the machine, indeed.
Ive had some pretty great ghosts in the machine… my X-65F for the longest time would have random stick inputs. Like, I could take my hand off the stick, watch the setup page, and watch the stick position wander around in the square. Swapped for a new one courtesy the warranty department - no fix. Plugged into a new computer, just fine… but other types of stick worked fine in my rig too.
my working hypothesis is that there is some ungrounded stray voltage somewhere that is present in my USB circuits. Not being a hardware expert, thats my best guess.
Yours I would not accuse of random voltage variances. screwy stick board is the lazy diagnosis.
-
I cannot get the DX mapper application you guys linked me to to work. It spazzes out every time I try to load it.
I’m run Win7 64 Bit, would that be an issue?
-
I hope not. Ive not had any luck with it myself, actually. Win7 64 bit here too.
EDIT: Just loaded it fine here. Guess its not the OS at fault.
-
I hope not. Ive not had any luck with it myself, actually. Win7 64 bit here too.
EDIT: Just loaded it fine here. Guess its not the OS at fault.
Okay, I will give it a run when I get home (I know it will fail) but I will describe for you in obscene detail that will make you want to curse my children exactly what it’s doing and you can tell me what a dumbass I am for not checking the one box that would solve my problem but I don’t even know exists.