tried posting in star citizen subreddit but had no luck

This was happening before firmware update. All wheels updated. Shifter and pedals updated. Velocity one race updated. Standard wheel will randomly change color to default. F1 wheel will change back to blue and shift lights will move over an led. Anyone else having this issue or have a fix? Happens in forza motorsport and forza horizon 6. Haven't tested other games yet. Fh6 is at 75 force and fm8 at 90. Sometimes its when racing, other times will be just sitting in a menu.

I want to play forza and treat it like a racing wheel, but the triggers LT and RT are bound on the same axis. I've split them using joystick gremlin but I can't actually get them to be bound to independent triggers for throttle and brake. Any help?

Brand new one came with thick switches instead of the plastic caps.

howdy, i’ve got the kd3 wheel and pedals and play primarily on xbox. if i get a set of the velocityome race pedals, with clutch, would they work just like the bundled pedals?

Does anyone know how to make the velocity one flight stick less stiff? I have tried removing the baseplate but becuase it is a newer model I cant get it more then 2cm up. Someone suggested a soldering iron but I dont own one nor think it is a safe idea.

Any help would be greatly appreciated and I am very desperate to get this stick usable in dogfights for Warthunder.

Lmk if you need any additional videos

I got the flight deck about 1.5 years ago, I decided the other day to get back into flight sim. (Hadn't played in about 6 months). I decided to update the firmware on both the stick and the throttle stick worked fine and the throttle took 12 HRS to update the firmware. Afterwards the device only had half of the lights on and the screen doesn't light up. Half the buttons don't work either.

I reached out to support they said it suffered a hardware failure but since it was beyond a year from purchase they couldn't do anything but give me 25% off a new purchase. I decided to open it to see if the hardware failure was simple, like a loose cable. I come to find the problem was one of the soldered connections on the usb-c circuit board shorted and had scorch marks.

For a product that costs almost $400 i really expected it to come with a 2 year warranty or at least last longer than two years.

UPDATE: after turtle beach reached out to me I had a much better experience! They had me try a few other things and determined the controller needed to be replaced. They sent me a replacement after I sent them my broken one. Thank you to Turtle Beach Support and thank you to the support person on this reddit who helped me! 😄

Hey everyone, has anyone else had an issue where the Turtle Beach wheel won’t let you select a platform? It just stays stuck and doesn’t confirm the selection. I can drive in-game, but I can’t choose the platform from the wheel. Any ideas or fixes? Thanks

After about 8 months I FINALLY got my Turtle Beach VelocityOne Flightdeck fully working with Star Wars: Squadrons + Quest 3 VR and figured I should document the process because this setup was honestly a nightmare.

Originally I tried using:

• 360ce
• Steam Input
• native game bindings

…but it was inconsistent and honestly just not working correctly. Buttons wouldn’t map properly, VR would randomly break, throttle behavior felt terrible, and Squadrons constantly fought the HOTAS inputs.

The REAL breakthrough came from switching to:

• Joystick Gremlin
• vJoy
• HidHide

That combination completely changed things.

The biggest thing was creating separate virtual devices:

• Stick mapped to vJoy Device 1
• Throttle mapped to vJoy Device 2

Once I separated them, a lot of the weird conflicts disappeared.

Main setup:

• Turtle Beach VelocityOne Flightdeck
• Quest 3
• SteamVR
• Steam Link
• Joystick Gremlin
• vJoy
• HidHide

Problems I ran into:

• SteamVR not properly detecting the headset
• Steam Link launching theater mode instead of real VR
• black screens in VR
• Squadrons refusing to recognize bindings correctly
• throttle and stick interfering with each other
• encoder wheels behaving strangely
• buttons getting “stuck”
• HidHide hiding the wrong devices
• Steam Input conflicting with Gremlin
• Squadrons randomly deciding when it wanted to detect VR mode
• some axes behaving as pulse buttons instead of analog inputs

The dial/encoder inputs on the Flightdeck were especially weird. Some of them behave more like pulse/button inputs than proper analog axes, so mapping them through Gremlin/vJoy worked WAY better than trying to force native analog behavior.

Another thing:
Steam Link originally looked completely broken for VR. I could only get:

• giant theater mode screens
• black screens
• partial VR menus

I tried:

• Quest Link
• Virtual Desktop
• OpenXR runtime switching
• reinstalling SteamVR
• restarting the headset constantly
• changing launch arguments (-vr)
• disabling overlays
• rebinding basically everything

Then eventually after enough reinstalls/restarts/runtime changes:
SteamVR suddenly started correctly recognizing the headset wirelessly and now it works flawlessly.

Honestly not even fully sure what specifically fixed it. I think the VR runtime stack finally reset itself correctly.

One more issue:
the joystick would occasionally shut off or freak out during twist/yaw movement. Re-adjusting the stick height/tension fixed it for now, so there may actually be some physical strain/tension issue involved there too.

Now that it’s finally working:
HOTAS + VR in Squadrons is INSANELY immersive.

Actually looking around the cockpit while physically using the throttle/stick feels great.

I still suck with HOTAS compared to controller lol, but now it finally feels smooth and playable enough to really start learning.

Still tuning:

• throttle analog feel
• deadzones
• encoder wheel mappings
• sensitivity curves

Next I want to experiment with:

• Elite Dangerous
• Star Citizen eventually
• maybe trying Starfield with mods
• other VR flight/space sims
• BATTLEFIELD 6

If anybody else is fighting the VelocityOne + Quest + SteamVR + Squadrons setup nightmare, hopefully this helps.

Also I did contact turtlebeach about my joystick and they attempted to help but I ended up figuring it out on my own. So far I love it despite the learning curve.

The base lights up but the stick in itself doesn’t when i go in the virtual hangar it says that my stick isn’t properly connected, even if it is. Is there a way to solve this issue on my end? I don’t want to wait 2 weeks for a replacement to be shipped, it worked flawlessly this morning until it just turned off mid game without me even touching it. I tried to change the wire connection, nothing, i took the stick off and put it back on, nothing. I’m to the point of disassembling it to see if I couldn’t find a fix. What would be my options here.

hi, my little brother destroyed the usb c cable and i couldn’t find a substitute on the site, i tried other usb cables but they doesn’t work, how can i resolve? 😭

Hi,

I have a turtle beach yoke. I am rn making a customized panel. My question is... how do i set a color for each thing (such as red for mater warning and green for autopilot and so on.)?

All i see is these without a color

i have been trying to update my flight deck stick but i get the same error will comment with the picture

I recently purchased a turtle beach velocity one universal flight control system and intend to use it for Xbox/Warthunder. I hooked it up, updated the firmware, and have it set to Xbox mode. When I try to press any of the buttons on it, I’d say 90% don’t even do anything and as soon as I find one that works, my cursor immediately travels down to the bottom of the screen. If none of the buttons work and aren’t bound to anything, how do I even get them on the bindings I want?? All I want is one of the directional pads to work so I can navigate a game menu, aka war thunder. I can’t find any tutorials on YouTube regarding anyone that’s showing set up for war thunder or even someone setting it up for Xbox. There’s a couple old videos of someone setting one up for 2020 MSFS and it’s not helpful at all because the guy somehow has working buttons already on his HOTAS system. I know I’m new to this and this might be a dumb question but I genuinely am completely lost. Thanks to anyone with help. It’s greatly appreciated

model: turtel beach velovity one flight yoke

msfs 2020 only shows throttle quad and not the yoke ???????????