Hi, I have FSX running pretty nicely now on my PC, however the planes in FS2020 are utterly uncontrollable. It's nearly impossible to keep them on the runway never mind take off without crashing. They just shoot off in random directions and flip over and crash if they get airborne at all.

I also have the same problem with P3D.

I would have thought lots of people run more than one flight sim on their PC, but unless I am doing something wrong with both FS2020 and P3D v5, it seems the only one where I can have controllable aircraft is FSX. That was the first flight sim on my PC.

Is this normal, or could anyone point me in the right direction for a solution? I have had several goes now over a few weeks without success.

Thanks

 

 

 

Edited September 7, 20205 yr by WestEnd

That's not normal. What controllers are you using? And make sure to map axis to the axis inputs. It's very easy to make that mistake in MSFS.

I am using a Honeycome Alpha Yoke, and Thrustmaster pedals and a Thrustmaster throttle.

I'm not really sure what you mean by mapping axis to the axis inputs, but I do have all the axis that I want each controller to control assigned to that controller, and removed from any others. EG, the thrustmaster throttle also has a joystick attached, but I have removed the elevators and alileron axis from the joystick so only the throttle is operational.

Until yesterday I was using a CH Products yoke and rudder pedals and I had the same issue, so I don't think it is specific to my actual hardware. Hopefully there is something I need to do in FS2020 and P3D v5 that will have the aircraft controllable.

It's certainly not normal. I had FSX:SE, P3Dv4, and XP11 on my system together for years, without a problem.

4 minutes ago, JDWalley said:

It's certainly not normal. I had FSX:SE, P3Dv4, and XP11 on my system together for years, without a problem.

That's good to hear. Hopefully that means I can get my issue sorted.

Sounds like something is off with your controller calibration and / or with the axis sensitivity settings. May want to have a look here (need a subscription):

https://forums.flightsimulator.com/t/how-to-calibrate-your-joystick-yoke/129335

Edited September 7, 20205 yr by RudyB24

3 hours ago, WestEnd said:

I'm not really sure what you mean by mapping axis to the axis inputs,

If a control action in MSFS does not have the word axis in it and it's mapped to an axis, that is wrong.

For example, the control menu shows Elevator mapped to your pitch axis on your joystick, that is wrong. It should say Elevator Axis.

Ah, Ok. I'll check if I've done that wrong. Thanks

I checked to make sure 

14 hours ago, RudyB24 said:

Sounds like something is off with your controller calibration and / or with the axis sensitivity settings. May want to have a look here (need a subscription):

https://forums.flightsimulator.com/t/how-to-calibrate-your-joystick-yoke/129335

I had a look there thanks. 

I must have calibrated my controllers through Windows 100 times trying to solve this problem to no avail.

Or at least I have calibrated them as much as I can. Rudder pedals have no button to press when Windows tells you to press a button, and when I try to calibrate my Honeycome Alpha yoke nothing happens when I press a button when Windows calibration tells me to, even though the yoke buttons work in the flight sims.

Until 2 days ago, I was using a CH Products yoke and pedals, and I had the exact same issue with P3D and I'm sure with FS2020 too. That was one of the reasons I ordered new controllers. The last 2 days I have been using Honeycome Alpha yoke, Thustmaster pedals, and Thrustmaster Hotas X as the throttle.

I just tried playing around with calibration settings within P3D there. I put the rudder sensitivity right down to 1, as the slightest touch sent the plane violently to the side. I was able to fly the pattern fine in a Cessna, and land again uneventfully. The second time flying the pattern, it flipped me over and dived into the ground just before I turned for final, even though I hadn't moved any controllers. 

I then put all the sensitivity and null zones settings to default in P3D and tried that. As soon as I took off, the Cessna pulled violently to the left, then flipped over and dived into the ground. 

Just to reiterate, I am having no problems with FSX SE, but using the same controllers with the same Windows calibration has the aircraft in P3D and FS2020 uncontrollable.

Oops, that is very frustrating. The only positive seems to be that the controllers work well in FSX, which means they are calibrated and are recognized well in windows as such.

But why do they not work in P3D and MFS? That's a mystery. Have you tried a search for 'honeycomb' in the MFS forums? Or more general,  a search for 'joystick'? Who knows there is someone with similar issues and maybe a solution is buried somewhere in the many posts there.

Edited September 7, 20205 yr by RudyB24

It looks like I'm getting somewhere now.

I found another post on the P3D forum about switching control input method from direct input to raw, meaning you could then calibrate within P3D.

That may or may not have made a difference.

However, I have found turning the sensitivity of my yoke and rudder way down, with a big null zone on the rudder, and no null zone on the yoke is now giving me a nicely flyable A2A Cessna.

Hopefully that is my issue resolved. It seems a little bizarre that the sensitivity settings set wrong mean you have an aircraft that is trying to kill you, rather than just one with more responsive controls.

 

now that it looks like I'm sorted in P3D, I can try to do the same thing in FS2020.

 

What you are getting is indeed strange. I have the Honeycomb Yoke, and had a CH Eclipse before that. I went through the entire Alpha program with the CH, and got the Honeycomb for the release, and they both worked great. Wish I could be of more help...

 

Russ

I opened a thread yesterday about this, now it has disappeared somehow!

My MSFS has been working very well, using the controllers what are in my signature. I have FSX on another computer using the same equipment and no issues. Yesterday, I decided to load up FSX on the same computer as MSFS, but I am experiencing your very same problems on both FSX and MSFS!

What I have noticed in the control options of MSFS is that the left had side axis does not show the white bar when placing the joystick to the left!

My impression now, after reading your comments, is that perhaps it is difficult to have FSX on the same computer as MSFS.

If the FSX/MSFS running on the same computer is causing the issue, then why would that be? There should not be any interaction for that to happen. I have FSUIPC4 working with FSX and FSUIPC7 working with MSFS. Apart from that, MSFS issue is with the joystick and on FSX I noticed that the joystick and rudder pedals were playing up - pushing the left pedal the helicopter took off!!!

I'm going to try MSFS again now and, if necessary, disable FSUIPC4 and do the same with FSUIPC7 when running FSX.

Martin

Update on my previous post:

I looked at both FSUIPC4 and FSUIPC7 - nothing to do with them causing the issues - for my setup anyway.

There is a major conflict between the calibration and sensitivities between FSX and MSFS. Somehow the controller button keys in the FSX setup had completely been set to different buttons which I had previously set. I confirmed that flying in both sims was not possible in various planes/helicopters tested.

I reset the FSX buttons to what they were and there was perfect flight throughout.

I did not change any control settings in MSFS. Result, perfect flight! In my opinion there is a certain amount of FSX controller input with that of the controller calibration within MSFS.

This could be a bug, but would require input from MS/Asobo to clarify this.

Trust that this helps!

Martin

Have sent a request to Zendesk to look at this

Edited September 8, 20205 yr by sauviat
Sent to Zendesk