Sim Rate - once you use, it's always 'armed', resulting in unintended sim rate changes

Description of the issue:
When the simulation rate is adjusted in a flight session, it stays “armed” so that even after the sim rate is reset to normal speed, it still gets unintentionally altered when using certain controls. Specifically, on my Xbox-style controller (where I use the triggers as rudder inputs), pressing the left trigger (LT) will now decrease the sim rate, and pressing the right trigger (RT) will increase it. This causes issues, as now every time I rudder with my triggers, the sim rate changes. This leads to losing control and crashing the aircraft, making the session unplayable after any initial adjustment of the sim rate. To fix this, I need to restart the entire simulator—just leaving the flight and returning to the main menu isn’t enough. The program must be fully closed and reloaded to stop the sim rate from changing with the rudder inputs. If I adjust the sim rate at all in this new session, I have to again repeat this process. Because of this, adjusting the sim rate is never a viable option.

Note, that I have no sim rate controls bound to my controller; only the keyboard. I initially assumed LT and RT on the controller were somehow permanently tied to “minus” and “plus” functionality, and therefore perhaps why they were adjusting the sim rate after an initial use. I thought this because my keyboard bindings were “Shift±” and “Shift+=” to decrease and increase the sim rate. However, I have been experimenting with different keyboard bindings for adjusting the sim rate. No matter what I bind it to, once I use sim rate a single time, my trigger buttons on the Xbox controller then will continue adjusting sim rate up and down as I rudder right and left respectively. This seems to be a bug.

This issue occurs on both Xbox Series X and PC versions of the sim.

Somewhat related, I’ve encountered another bug. When binding button chords (using one button as a modifier to unlock more binding potential on a device), some of the chorded bindings won’t work properly. Instead of activating the desired action, the individual buttons in the chord will all execute their commands simultaneously. For example, as mentioned above, I bind left and right rudder inputs to LT and RT, while I zoom out and in using the chorded bindings of LB+LT and LB+RT. This worked as expected in MSFS 2020 (on both Xbox and PC). However, in MSFS 2024, using these bindings results in both the rudder input and the zooming happening together. Interestingly, this issue only occurs in external view, and only on Xbox. The PC version of the sim does not seem to have this bug.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
I am running 100% vanilla.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time I try to adjust the sim rate.

REPRODUCTION STEPS

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

  1. Alter sim rate
  2. Return sim rate to normal settings
  3. Xbox controller triggers will now somehow alter the sim rate whenever pressed.

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:
On PC, just an Xbox style controller. On Xbox, an Xbox controller and (sometimes) I add mouse and keyboard. I also recently added a VelocityOne Flightstick to my Xbox setup, though the problem was happening before then. I honestly don’t think it’s related to peripherals, but more that LT/RT somehow seems linked to adjusting sim rate, but only once sim rate adjustment feature is initially used.

[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; this is an MSFS 2024 issue.

[PC Only] What GPU (Graphics Card) do you use?
Nvidia RTX 3080 Ti

[PC Only] What other relevant PC specs can you share?
Windows 10 x64
AMD Ryzen 9 5900X
32GB RAM

MEDIA

Please add a screenshot or video of the issue occurring.
Unable.

[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:

Specifically, the PLUS and MINUS stay bound to the sim rate control… so when using the BRAVO and increasing for example your ALT (this uses a PLUS command) your Sim Rate shoots up.
I cannot understand how this is not a bigger issue and only two votes..?!?!

To confirm – does this happen even after selecting another variable with the selector knob on the Bravo? (As opposed to leaving it untouched?)

Note there are also ‘increase sim rate’ and ‘decrease sim rate’ bindings which afaik don’t change the selected variable; try with that instead of the “sim rate” selector and then “plus”/“minus”. I don’t recall having any surprises using that way in 2024.

This is definitely a THING!

I thought I was going crazy until I started doing some very close monitoring of what was going on - the sim rate appeared to be resetting itself when adjusting the controller knob on the Bravo. This is despite me using a blank Bravo profile in 2024 (as I used SPAD).

Its bad enough that once again there is no indication of the sim rate in use and even that the in-cockpit clocks don’t change their rate either (which makes me think that the sim rate doesn’t alter TIME, but rather SPEED). What a mess!

1 Like

I’m experiencing something similar. I’m still trying to figure out if I’m accidentally toggling the SIM RATE command first and then it goes haywire (usually during landings when I’m close to the ground :slight_smile: ), or if it’s going haywire without even touching the SIM RATE commands.

Edit: Yeah nah, it just goes berserk. Unknown cause but extremely annoying. Please fix, Asobo!