Hi. I got a new pc in January, i7 proc, 4tb ssd, 16gb memory, nvida gforce rtx.

I also got a Turtle beach, velocity one flight yoke, rudder pedals and flight stick.

Plus the Steam version of SMFS2020 flight sim.

Since then I have spent considerably more time trying to calibrate and map the controls than 'flying'

No matter what I try, it seems to start up with slightly different settings and often I restart the game and get different things happen again. Most of the time on level flight in calm conditions, with everything set on the easiest settings ( everything AI) it banks to, usually the left side and flys in circles or just drops out of the sky. I have tried auto trim on off and even deleted from my settings. Sometimes the rudder does not go fully one way and just judders.

As it does this with both the velocity one flight yoke and the flight stick, I tried my old Logitek attack 3 and although it did not link up with many of the controls it does the same same thing with the basic flying controls, which were working.

I then hooked up the velocity one to my 14 year old pc running windows 7 and FSX.  FSX would not recognise the flight yoke but did work perfectly well with the flight stick.

I am wondering if MSFS2020 is actually compatible with any Turtle Beach, Velocity One products? I know there are many videos on YouTube etc, showing how well they work but on my set up, I cannot even follow their guides as half of the bindings have different names. I am by the way, not trying to set it up using the XBox settings, even though the default controller headings say XBox.

It is all very frustrating but I seem to get better results from FSX even if the graphics are rubbish by comparison, it at least flys straight!

 

Cheers

Ron

 

Apparently it works for some....

 

8 hours ago, ron6a said:

I am by the way, not trying to set it up using the XBox settings, even though the default controller headings say XBox.

I'm not understanding this. Is the yoke's input set to Xbox or PC?

I was going to ask the same thing about making sure your flight stick is in PC mode and not Xbox mode. I use the velocity flight stick in 2020 and 2024. The only thing my flt stick doesn't run is the rudder which I use pedals. I was able to find all my bindings, just type in what you want and search for the key bindings and set it.

I do have both the f/stick and the pedals - but use the pedals on my PC and my f/stick on my Xbox- so

unfortunately, I cannot comment on them both on the same console

However - I note that the F/stick came new with the twist grip as default rudder so just check that you have reset

that to something else in case it is interfering with your pedals

Also - as someone else said - make sure that the pedals are set to PC - and the light on the pedals is white

I repeat - the stick comes with strange default settings and comes in the X box default mode

Similarly - I dont have the yoke - but the setups are very specific as to the correct use of the cables that 

came with the 3 controls - and I dont see how the three controls can be used at the same time.

 

I doubt it has anything to do with the controllers.  I used the Turtle beach stick and it works just fine in 2020/2024.

Chances are, you have duplicate assignments that are conflicting.  

It has been awhile since I was in 2020's settings, but you need to look at every assigned function for every device.  If you have rudder pedals, those might be assigned, but it also might be trying to use the twist axis on the stick (which you obviously don't want with pedals).  Those 2 things will fight each other and cause what you are seeing.  

You need to go through all the controller assignments and delete anything you don't want.  MSFS tries to be "smart" but often it will do things like this.  

Edited April 23, 20251 yr by kerosene31

On 4/23/2025 at 4:24 AM, Twenty6 said:

I'm not understanding this. Is the yoke's input set to Xbox or PC?

This running on a PC.  I don't know how to post photos on here but on Microsoft Flight Simulator 1.38.2.0 in controls options the yoke is described as

CONTROLLER (XBOX 360 FOR WINDOWS)

YOKE - SINGLE-ENGINE PROP.

 

and the Velocity One Flight (not flight deck) says input mode: PC  firmware 1.5.0

2 hours ago, ron6a said:

This running on a PC.  I don't know how to post photos on here but on Microsoft Flight Simulator 1.38.2.0 in controls options the yoke is described as

CONTROLLER (XBOX 360 FOR WINDOWS)

YOKE - SINGLE-ENGINE PROP.

 

and the Velocity One Flight (not flight deck) says input mode: PC  firmware 1.5.0

Have you done the checks that we have been suggesting to you?

Your last line begs the question - have you updated the firmware on all 3 controls?

does your windows control panel recognise all your 3 Turtle bits?

msfs in the controls heading section uses the term controller as an X box controller - which it is - not any other

have you got an x box controller attached to your PC?

The control section will always recognize your peripherals as what they are called by the manufacturer

1 hour ago, ron6a said:

This running on a PC.  I don't know how to post photos on here but on Microsoft Flight Simulator 1.38.2.0 in controls options the yoke is described as

CONTROLLER (XBOX 360 FOR WINDOWS)

YOKE - SINGLE-ENGINE PROP.

 

and the Velocity One Flight (not flight deck) says input mode: PC  firmware 1.5.0

In my control options my flight stick is described as Velocity and my Xbox controller is labeled as Xbox controller and my rudders labeled as CH rudder.

I purchased the pedals just a couple weeks ago, using them on both 2020 and 2024, of course you have to set configuration correctly, but given that they are awesome, no problems.

 

3 hours ago, ron6a said:

This running on a PC.  I don't know how to post photos on here but on Microsoft Flight Simulator 1.38.2.0 in controls options the yoke is described as

CONTROLLER (XBOX 360 FOR WINDOWS)

YOKE - SINGLE-ENGINE PROP.

My Controls Options shows:

VELOCITYONE FLIGHT with the Description window showing a picture of the Yoke

VELOCITYONE FLIGHT with the Description window showing a picture of the Throttle Quadrant

It's listed twice and I don't know why they did it like that. But that's what it is.

My guess is that when you started MSFS2020 with the VELOCITYONE FLIGHT plugged in it was in XBOX input mode which is why Controls Options is telling you "CONTROLLER (XBOX 360 FOR WINDOWS)". It's stuck on XBOX mode.

I would try unplugging the yoke and throttle quadrant while MSFS2020 is running to see if the VelocityOne Flight profiles disappear. If they don't disappear you're going to have to figure out how to make them disappear. I remember there being threads here on Avsim to delete hardware profiles so search. Once they're gone close down MSFS2020 and then restart. Back inside the Controls Options menu make sure the throttle quadrant is plugged into the yoke and the VelocityOne Flight is in PC input mode. Plug it into a USB on the computer and hopefully everything is OK. TurtleBeach does not recommend using USB hub.

Thanks all for the tips.

 

1 hour ago, ron6a said:

Thanks all for the tips.

 

So! - don't keep us hanging - what are the results ??? - have you got it all sorted ??

After a fashion.  I unplugged the controller mid game, to no effect. 

Reverted back to version 14 of the yoke and controller. 

Did a new blank profile and input the bindings from scratch. 

It still displays  xbox controller for windows  but flying ok ish. It still banks left a bit but nothing badly. I am flying in real time and weather and am happier with the results. 

 At least my landings are better than the AI pilot's. 😁

3 hours ago, ron6a said:

After a fashion.  I unplugged the controller mid game, to no effect. 

Reverted back to version 14 of the yoke and controller. 

Did a new blank profile and input the bindings from scratch. 

It still displays  xbox controller for windows  but flying ok ish. It still banks left a bit but nothing badly. I am flying in real time and weather and am happier with the results. 

 At least my landings are better than the AI pilot's. 😁

When was the last time you updated your Velocity one's firmware?