Descent stop working as soon as landing gear is down

Hi CMDRs,

Doing exobiology currently, I need to land on planets.
Since mid past week (so ~Dec 18), I have the following issue :

In all others conditions, my thrusters (up,down,left,righ) work perfectly, so my hota (X52 Saitkek) does as well.
On planetary approach phases my descent command still work (thruster down), but as soon as I deploy my landing gear it stops working.
Other thruster commands still work however (left,right,up).

Issue is that to land, this is a weird problem, so I am obliged to use automatic landing since that time, that is really annoying.

As in an expedition, far from any base, I could not try to land on a station yet so do not know if this would work or not.
Obviously, I did not modify any option settings.

Is it an issue one of you ever encountered, or is there a hidden code line somewhere saying something like "Cmdr=='SparcT1' ? abort(randomly) : proceed(normally)" ?
Thanks in advance for any feedback,
O7,
SparcT1.
 
Sounds like either
a) an issue with your stick or
b) an issue with your controller setup that switches to a different profile (check the bindings error log) or
c) you (or someone/-thing) configured the "landing override" functions. ED provides two sets of thruster controls, one for gear up and one for gear down. Intended as far as I can tell for gamepad users and others who are lacking in a sufficient number of axes/buttons.
 
Hi Ashnak,

Sorry for late answer but was in session quite all day.

So, about your suggestions...
a) an issue with your stick or
b) an issue with your controller setup that switches to a different profile (check the bindings error log)
... well, no hope. My X52 thruster commands work perfectly as far I do not deploy landing gear. Also, only thruster down fails at that time. If something was wrong with the stick, it would be in any condition, but this is not the case. As far landing gear has not been deployed, anything works perfectly.
Also, my X52 is an old one (far before the X52-pro, so 10+ years old. It still work as a charm, but (thanks to logitech) no more drivers are available for it. No backward compatibility with the X52 pro that is just a cosmetic review of the original one, but has a different USB SN so drivers refuse to install. That means : No profile, buy a new one ... Are those guys kidding ? Dropping a device that works perfectly simply because they don't want it to work anymore for their business... Well, anyway this is off topic.
c) you (or someone/-thing) configured the "landing override" functions. ED provides two sets of thruster controls, one for gear up and one for gear down. Intended as far as I can tell for gamepad users and others who are lacking in a sufficient number of axes/buttons.

I searched for such options. Could not find them. As well my config files were untouched for more than 4 months. So...

Just as the situation was really annoying for me, I did a break in my trip and went to first available station at about 200 LY.
Same issue for docking on a star port.
As soon as land gear is deployed thrust down (and only this one) stop working.
Obliged to go to automatic landing.

On planet landing I found a walkaround however : I stay high, deploy landing gear and then while it is deploying, I use the thrust down. Then it works, and still continue, but well... doing that within a station... would not like to have a bounty on me ;-).
Without this trick, at first time thrust down fails on landing, it will be totally deactivated for session time or planet time, gear down or not. ( had to go orbital, then back, to restore normal status - then it worked again).
Also, "sometimes", doing a first landing in automatic mode (thrust down killed), then going back to manual landing restore (temporarily) the thing.
Finally, the primary key 'F' by default still works "sometimes".
As I had no issues before and it suddenly appeared mid past week, I do not understand...
I guess Frontier did not do any updates by that time, and for such issue, I think I would not be alone facing it, so, really... I do not understand.

However, thanks a lot for your answer @Ashnak

Cheers and O7,
SparcT1.
 
I searched for such options. Could not find them.
1734895430915.png
 
Without this trick, at first time thrust down fails on landing, it will be totally deactivated for session time or planet time, gear down or not. ( had to go orbital, then back, to restore normal status - then it worked again).
Ok, that is strange. I'm out of ideas.
 
i don't think gravity is bugged........................
goto external cam view the underside thrusters they must be firing to stop a gravitational decent on an airless moon🤷‍♂️
turn your thrusters off in the right hand ship module control panel that will inform you of a binding error somewhere?
as when you do thrusters will not fire & you will fall/descend
check the landing gear binding has only one single bind and flight landing overrides all remain unbound its that simple
(dont test this on a high g moon btw)
 
Last edited:
Hi All,
Sorry for late answer, but end of year is traditionnaly somewhat of a blackout on my side.
By the way best wishes to all and you families for the new year !

Regarding my issue, I do not understand, really.
I have re-inspected any of my key bindings : anything is perfectly fine.
Sometimes, it work nicely, sometimes it does not, and sometimes then it work again (or fail again - or re-work again between two landings/take-off randomly).
Without landing gear deployed, the thrust down key works perfectly in all conditions (i.e. when mining).
I have found workarounds anyway : First is the keyboard key 'F' (work anytime). Second is retracting/redeploying land gear (work sometimes). Third is jumping out of orbite then entering again (then works again... for sometimes).

So, well, I do with those workarounds and that's OK, even if far being perfect, so far.

Cheers to all and happy new year !

O7,
SparcT1
 
Hi,
I have the same joystick:- I use the 3 modes, mode 1 for normal flight, mode 2 for landing, and mode 3 for surface driving.
You can test the joystick operations by using the run command and “joy.cpl”. This will let you check the operation of all the buttons, sliders, and toggles.
The x52 drivers are (or were) on the saitek download page.
One thing I have found is that occasionally is appears that Steam interferes with a fight arrow binding. Closing Steam seems to rectify that…
 
Hi Colprice2002,

Sorry I did not see your answer sooner.
In fact I have no more Saitek original drivers, and Logitech do not distribute them anymore.
So, I do with what I have.
On other other hand, after 10+ years of service and duty, I'm a bit asking myself about an X52pro.
(It's doing some kind of "crouic-crouic-crouic" as I move the stick, I discovered new hard points on the thrust, and he really look ... well.. very used)
However, not for now.

Cheers,
O7,
SparcT1
 
Back
Top Bottom