ISSUE DESCRIPTION
Left brake axis does not work on the Turtle Beach Velocity One Flightstick. Only right brake axis works, causing the aircraft to veer to the right when braking. I bind both left and right brake axis to the right throttle lever, allowing for smooth brake inputs. Both bindings show they are bound, but only the right brake axis works.
FREQUENCY OF ISSUE
every time on sim load
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
load any aircraft that supports left and right brake axis
-
give aircraft throttle to get the aircraft moving.
-
add brakes by sliding the Turtle Beach VelocityOne Flightstick lever forward.
YOUR SETTINGS
What peripherals are you using:
Turtle Beach Velocity One Flightstick
I’m using Xbox controller on PC and encountering the same issue.
I bind The left and right brakes to the same axis(Y-axis of left stick). At start it works fine, but once pressing some buttons simultaneously, only the left brake becomes unresponsive for same axis input. This issue can be seen on all aircraft in SU4. (In SU3, it works fine.)
Nothing happens with undefined button combinations. This only happens with combinations defined on the app’s settings. So I think there might be something wrong with the app’s input system. In any case, I hope for a quick resolution.
This has been happening to me since last week when I tried the beta version .31 (I joined the beta last week only as I heard good stories about it). I’ve been trying to find ways to fix this through remapping but it still comes back after a while. No cause effect found (and I have limited time to spend in trying to research this). It works well at first, but after a while, it stops working. And surprise! When you land with only one side brake. It happened regardless of the planes flown. XBOX -X, with Thrustmaster Hotas one the 2 brakes axis programmed on the throttle rocker. This allows to modulate braking (the on/off brake digital control is a definitive no-go) Only the right brake works.
I thought I would update on the situation. The problem is clearly intermittent, hard to find the cause and to reproduce it. I flew for a couple of days without problems and today I flew from Hobart in Tasmania to Queenstown NZ. Used the PC-24, no problem. After landing, I wanted to try landing a plane I knew well, so I flew the 930 in on RW 05. So when I finished my flight with the PC24, I switched to an approach only with the 930 and then when I landed, the problem occurred again, only the right brake was working, surprising me and pulling me out of the runway… It’s the second time it happens with the 930. A few days before it was working well at takeoff and when I landed, it stopped working. I hope this helps.
I’m really struggling with this issue so I’d like to report the situation. In my case, I was able to completely reproduce the issue using the following steps:
1. Preparation
-
This is not essential, but to keep things simple, first clear all the settings in the controller.
-
Bind the left and right brakes to the same axis (ex. Y axis of L stick, it doesn’t matter which axis)
-
Bind any function to two simultaneous button presses (ex. LB+Y, functions and button types don’t matter)
-
Start flight (Leave it spawned)
2.Survey
-
Move the assigned axis and check that both brakes respond by observing the pedal movement.
-
Operate any button combination except 1.-3), then try operating the brake.
-
Operate the buttons assigned in 1.-3), then try operating the brake.
3.Results
Case2.-2) The brakes work correctly.
Case2.-3) The left brake is stubbornly stuck and there is no recovery.
I have confirmed this issue on C172, A32N, Icon A5, FENIX A320, ini A350, etc. in SU4.
It doesn’t happen with a single button setting for 1.-3).
It doesn’t happen in SU3.
It happens with both genuine and third-party controllers.
I hope this helps to solve the problem.
OK, since it’s the holidays, I had a bit more time to test, so think I’ve found the problem. It looks like it’s somehow multiple buttons or axis which was assigned to a single function. In My case I had the reverse throttle assigned to the reverse trust hold + the axis. I think it was resulting in generating some kind of conflict once the trust reversers were activated, hence the problem with the TBM and not with other planes. I was able to reproduce the error and reconfigure the control properly. So far the problem is gone. So I think it’s worth it to check the key/binding assignments. For me, the problem seems to be resolved unless I post back. Cheers!
The same bug remains in SU5 BETA2. It’s been happening since SU4, though it worked perfectly in SU3. Looking forward to a quick fix.
I have this same issue with SU4, tested day of posting. I find that switching to external view can trigger the lock up, which can then only be temporarily undone by unbinding the left brake axis, saving, returning to sim, pausing, rebinding left brake axis. Disruptively annoying, as brake axis offers so much more control compared to button-bound brakes. I have confirmed absolutely no double bindings. Occurs in both default and third party aircraft.