Throttle cutting out in supercruise.

Just as the title states. I've started having this happen to me every now and then for the last couple of weeks. I play with Oculus Rift (not important bit) and Logitech X56 HOTAS (the important bit). I'll be in supercruise and my in-game throttle will randomly go to complete zero and refuse to work no matter what I do with my physical throttle or keyboard controls. My stick still works, all my buttons still work on both the stick and the throttle. I can drop out of supercruise to normal space and my throttle works just fine. I can jump back into supercruise and most of the time my throttle will come back but sometimes it won't and I'll have to logout/login to get it to work again. I know this isn't a hardware issue because again, everything works just fine in normal space; the problem/bug/glitch only happens in supercruise. Has anyone else had this happen to them and/or do you know what the cause might be? Other than the "weird glitch" explanation.
 
You say even keyboard control doesn't change your throttle when this happens. Is this keyboard action just the increase / decrease control or do you have binds for 75% and 50% and do those not work either?

Assuming that nothing is successful then perhaps you have a conflicting keybind that is causing an issue? Just a wild guess there but I can't think of anything else that would cause it.

BTW - I assume you have done the "validate game files" already.
 
You say even keyboard control doesn't change your throttle when this happens. Is this keyboard action just the increase / decrease control or do you have binds for 75% and 50% and do those not work either?

Assuming that nothing is successful then perhaps you have a conflicting keybind that is causing an issue? Just a wild guess there but I can't think of anything else that would cause it.

BTW - I assume you have done the "validate game files" already.
The keys for increase/decrease as well as the 50%/75%. Neither work. Wouldn't be a conflicting keybind either because, as I stated previously, I can drop out of supercruise to normal space when it happens and my throttle works just fine. The problem only happens in supercruise.

Like when it happened last night; I was in supercruise in a system going in a straight line to a planet. Was about 12kls away, so I simply had the throttle to max and my hands off both the throttle and the stick just waiting to get there. Then without me doing anything, I went zero throttle for no reason. Game didn't bug out (other than this issue), no other ships around, no hiccup in internet. All my other controls still worked fine. Dropped to normal space and the in-game throttle immediately revved up since my physical throttle was still in forward position. Throttle up/down/reverse all worked fine. Jumped back into supercruise and throttle simply zeroed again. Had to logout/login and it fixed itself.

This issue has only happened to me.. 3 maybe 4 times within the last month. I would chalk it up to some wonky-ness of alt-tabbing to one of my other monitors to look something up (pulling my VR headset up for this obviously) and then alt-tabbing back in, but why would it ONLY happen in supercruise but work just fine in normal space, and ONLY affect the throttle in supercruise and none of the other controls?

EDIT:
It hasn't always been when I alt-tab out.
 
Last edited:
OPEN your bindings folder and open the binding errors log file what if anything does it say?
Here's the entire file contents:
There where errors when loading preset file: Custom.3.0.binds
Missing devices: SaitekX52
This is from when I first used an X52 setup before I upgraded to my X56. But again, I don't think it's a binding issue because it's happened without me even having my hands on the controls. I upgraded to the X56 around the middle of last year. This issue only started a few weeks ago.

EDIT: As an afterthought, I'm amused that the "were/where" typo isn't my own typo, but is actually misspelled in the file itself.
 
Last edited:
I had this it was the" reverse throttle " wich was messing around.

Maybe just for trying, set it to hold instead of toggle and see if the problem still occurs ?
I'll try that, though who knows if/when it'll happen again to me. Hopefully not when I'm actually trying to get something important done, lol.
 
Back
Top Bottom