Have had performance issues with the new VO Rudders. Running Xbox Series X, latest MSFS update, latest VO software update 1.4.0.
After successfully using the rudder control a while I now have them not responding to braking. The controls settings in MSFS reflect the Brakes being controlled by LB/RB (Button 5 and 6) and by the brake pedals on the rudder L-Axis 13 and 14. The rudder controls work fine.
In training Mode on the VO the brake pedals are responsive on the screen as working properly but “in game” no response.
Around the same time my trim wheel adjustment on the VO itself is acting strange in losing position at beginning of flights (full trim down) and then over time becoming useable. Also a few instances of it being non responsive.
I’ve followed all the troubleshooting tips own Turtle Beach. Anyone else having issues, any suggestions?
Yes I’ve had the same issue. Usually on the first boot up of system and yoke. My work around is turn on yoke. Go to Accessories > Rudder and turn it off. The yoke will power cycle. Then repeat the steps Acessories > Rudder and turn it back on this time. Has worked majority of the time.
I think it’s a issue with pass through mode not quite connecting all the bells and whistles.
I’m having the same exact issue. Usually the first game session of the day, works like a champ. Then turn on the xbox for another session and brakes don’t want to respond.
Training mode acknowledges the rudder brakes are being pressed but MSFS2020 doesn’t seem to recognize.
I’ve confirmed both Velocityone Yoke and Rudders are up-to-date on firmware. And MSFS2020 has the latest update as well.
I’ve power cycled the Velocityone set, turn off/on rudders in accessories, quit MSFS2020 and restart the software. This method so far has seemed to resolve the issue until the next time happens.
I guess I need to go into Control Options before starting a flight to confirm brakes are working. Loading a flight, getting set up to taxi, just to find out the brakes don’t work is very disappointing and time consuming. Hope there’s a fix in the near future.
Folks, I had the exact same issue as jimj2001. A good samaritan at cust support at VO sent me this and it fixed the problem. The trim is still set at -99 at first flight (Crazy…) but at least brakes work :).
If you have a VelocityOne Flight (VOF) and you’ve added the VelocityOne Rudder (VO Rudder) to it, but in MSFS the brakes are still controlled by the VOF and not the VO Rudder pedals:
First, let’s make sure the hardware is set up correctly.
To do this, go to the Training Mode function in the VOF.
Confirm that moving the VO Rudder axis on the pedals and the two toe brakes results in a test bar appearing on the Training screen. If not, the hardware is not configured correctly.
Even if the pedals are in Xbox mode, you may still need to go into the Accessory section on the VOF and enable the Rudder entry.
Once this is done, the hardware circuit should be correctly configured.
At this point, the Rudder axis on the pedals will function as the in-game rudder control in MSFS.
You will then need to manually assign the Left Brake Axis and Right Brakes Axis to their respective pedals.
In MSFS 2020 Control Options, make sure your brakes are mapped to L-Axis 13+ and L-Axis 14+ — NOT to L-Axis 13 and L-Axis 14 without a plus sign ( + ) after the numbers.
Please follow the above steps and let me know what results. Thank you.
Good info. The note on +13 v 13 for example was value added. I followed your process and had great results with the whole system running… until it didn’t. After a couple of starts and stops over 2 days went back to same old problems.
I have had TB replace one of my cables already (red) and I’m wondering if cables in general are a bigger part of the problem.
Also wondering if others have had coincidental issues with the rudder problems related to random wild swings of the trim wheel (max or min), random pitch issues that appear and disappear so fast not sure what actually happened, and lately random throttle loss- this one seems to recover if you move the throttle back to min and then max again.
Really discouraged. I think they designed and built a really great product but the software, or interface, or MSFS links, or whatever is being blamed lately, is just a complete lemon.
We’ve come to accept bad software in everything we buy; imagine other products that would require debug updates every single week like we get with software or iPhone apps etc. That philosophy now affects real world hardware products. I was a Day 1 buyer of both the VO yoke and the rudders, what a dummy.
All the same here. Brakes are hit and miss each time. So much so that I mapped the brake axis to the rudder pedals but also regular brakes to triggers so I don’t need to reboot the game each time. Shouldn’t be this way when you shell out so much money but I don’t think turtle beach will be seeing much of my money going forward.
Hello again, i have found a work around for this, which works since two weeks on my xbox x:
After starting the xbox normally and before clicking on the game icon, i go into the velocity one flight menue and deactivate the rudder under “accessories” (lights go off and on) 2. Then i start the msfs2020 normally 3. During the last booting sequence of the game, when you actual see the last game content liverages etc. and the blue loading bar is around 5o % done, i activate the rudder pedals again (accessories again).
Naturally don´t want to do this for my life and that there will come an offical fix for this;-) Hope it works for others too
Thanks for an easier work-around! Seems to be doing the trick…so far. Here’s hoping that TB gets enough complaints about this that they address the issue via a patch or future update.
but it’s a pain to have to swtich cables, do sets and resets, etc. (Not exaclty what I had in mind dropping those sort of funds for the rudder assembly!) What’s odd is that every time I’ve gone to recheck the update number (currently 1.0.1), while the yoke is fine, with the rudders, while it will show the latest update number, if I go ahead and do an update, it will redownload that latest update…again. It’s like it’s not getting saved correctly or something…
Great tips, thanks! I actually just joined this forum to respond to you and ask a question. When I go into “Control Options” - ALL-Brakes-Left (or right) brakes and Select an Input" it only scrolls down to L-AXIS11 +/-, no option for L13 or L14. Anyone else have that issue. Heads up, I’m ole and nearly computer illiterate!
I’ve run into the same issue with the proper inputs not appearing as an option. Lots of troubleshooting but the best advice i can give that cleared up most issues with the rudders is to disconnect your usb connection. After fresh boot of MS2020( im on xbox seriesx) then plug in you usbs. I use an unpowered hub with yoke/rudder, mouse, keyboard.
I do this each use of ms2020. This seems to clear up most of my issues. The nose dive from trim problem is mostly only remaining bug.
Having the same issue, surely turtle beach could at lease acknowledge the issue and say if they are fixing it or what, at the moment I’m contemplating seeing if I can get a refund because they’re more work than they’re worth.
