MSFS 2024 view constantly pitches down

User Support Hub Hardware & Peripherals
, ,
1

ISSUE DESCRIPTION

Description of the issue:

View constantly pitches down with no input. I went between MSFS 2024 and MSFS 2020 to compare and make sure it was not hardware related (video attached) - issue is only present in MSFS 2024.

If applicable, which aircraft is experiencing this issue:

Only tested FA18

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

No mods/add-ons

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Constantly

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start free flight in FA18
  2. Sit and watch view pitch down
  3. (also continues in the air)

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

Not relevant

[PC Only] Are you using Developer Mode or have you made any changes to it?

No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

N/A

[PC Only] What GPU (Graphics Card) do you use?

4070ti

[PC Only] What other relevant PC specs can you share?

5800x3d, 32GB RAM, Samsung 980 Pro NVME

MEDIA

Please add a screenshot or video of the issue occurring.

(copyright checking as of 8:21AM, should be available 8:31AM)

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

1 Like
2

If you have a POV assigned for looking around you could try a small dead zone on the vertical axis.

I had no issues in 2020 but had this issue in the horizontal axis so I added dead zones on both axes and have no issue now.

1 Like
3

Sounds like you haven’t added deadzones to your controller axises.
I had the same issue. Solved by adding deadzones.

1 Like
4

Hi,

We’ve moved this topic to the User Support Hub as the issue you are facing is likely due to peripheral hardware inputs needing to be correctly set up in the options menu, as per community comments above.

Thanks
The MSFS Team

5

Hrm - I never bind view controls to my HOTAS, and when I set up my VKB Gunfighter in MSFS 2024 I definitely never manually set that up. MSFS 2024 also didn’t bind any inputs that I could find by default - so it would be odd (but not unexpected for this product) if the only thing it chose to bind automatically was view.

That said, will check when I get home.

“I had no issues in 2020 but had this issue in the horizontal axis so I added dead zones on both axes and have no issue now.”
I’d say that itself seems like a bug? And if this is what the issue is, MSFS 2024 requiring a deadzone for a phantom input that isn’t present in MSFS 2020 sounds like an MSFS 2024 problem?

6

In my mind something that only affects certain controllers from some users is more likely to be the controller sending a very small control input at neutral that 2024 is able to read. 2020 possibly did have a higher signal threshold. This doesn’t necessarily mean it’s a bug though. There could be advantages to reading these smaller signals such as quicker and more accurate control response.

Controller noise has always been an issue and that’s why the ability to add dead zones is there.

If it only affects some users and some controllers and the tools are available for the user to fix it then I don’t see how that’s a bug.

7

Ah, gotcha. I don’t know how the signal processing works for these things, that makes sense!

(I’m a software engineering by trade so everything is 0s and 1s to me… but of course this isn’t a binary on/off signal ‘go up’ ‘go down’)

1 Like
8

Please be careful when you start programming quantum computers :slight_smile: Thanks. --Redeye

9

My head will explode. And it won’t.

10

Not sure how to mark this as RESOLVED

You all were very right. View pitch down had been mapped to my throttle’s mini joystick. Not sure how.

PEBCAK. :expressionless:

Sorry!

1 Like