Spurious motion data while in menu

[MSFS 2024] Bug Reports SimConnect
1

Version: 1.1.7.0 (SDK 1.0.0)

Frequency: On first aircraft selection

Severity: High

Context: While the game is still in the menu. Only on first selection of aircraft before the first flight.

Bug description:

Game generates spurious vehicle motion output in VELOCITY BODY X/Y/Z (and potentially many others) while the game is still in menu, before the flight has started. While SimConnect fails to properly report either SIM DISABLED or USER INPUT ENABLED or any other means an external application would be able to detect that simulation is actually paused (or at least not playable) this causes that we are picking up these updates and processing them as valid input.

Repro steps:

  1. Laungh MSFS 2024
  2. Go to free flight
  3. Select any aircraft (Guimbar Cabri G2 works best as it generates A LOT of spurious updates)
  4. Observe that VELOCITY BODY X/Y/Z data channels values change.
1 Like
2

I have the same problem - the telemetry is being sent, even when selecting an airplane or helicopter in the free flight menu.

I’m afraid that sooner or later I might get injured, because my rig includes two 750W servomotors for controlling the platform (pitch, roll and yaw), two 300W motors in the joystick and one 300W motor in the rudder pedals. and all of them are working in a dangerous mode, because the telemetry is not correct.

In other games (DCS, IL-2 and so on), telemetry only works when the player is in an airplane, airplane in the air or at taxiway.

1 Like
3

This video shows how there are strong impacts when changing helicopters.

2 Likes
4

The video is not the most dangerous case.

It can usually shake a lot (when loading a mission).

1 Like
5

Yeaaaaaa, I’d say that would need to rise to the very top of the priority list due safety risks. Don’t let MS legal see that vid!

6

Absolutely terrific and very dangerous issue for all ffb devices owners!

7

Yea that’s one of the reasons why I don’t use MSFS on my motion rig…

8

What motion/ffb software are you using? DRSM & VPForce have gotten around this using CAMERA_STATE to determine whether you are in cockpit

9

I use FlyPT Mover

10

Hello,

We have prepared a fix for this issue.

The core of the fix is that we now block updates of key motion parameters for the user aircraft while the user is in the Menu:

  • position and orientation
  • translational and angular velocity vectors
  • translational and angular acceleration vectors
  • total force and total moment vectors

For several reasons, we cannot fully stop aircraft simulation (including aircraft systems, etc.) while the user is in the menu, as certain in-game subsystems require the aircraft to remain “alive”. Therefore, we only block motion-related parameters for now.

Additionally, we now block updates of translational and angular acceleration vectors, as well as total force and total moment vectors, while in Active Pause mode (in the current version of MSFS 2024, as previously in MSFS 2020, only position, orientation, and translational and angular velocity vectors were frozen).

This change ensures export of fixed (last valid) motion parameter values via SimVars in situations where motion is not actually being simulated, and also resolves a G-LOC issue (pilot blackout) during Active Pause.

This fix should eliminate chaotic movements of motion platforms and FFB devices while the user is in the Menu or during Active Pause.

A known but currently unresolved issue remains: after exiting the simulation and coming back to the Menu, motion parameter values remain unchanged (last valid), rather than being reset to zero as might be expected, until the user selects another aircraft in the Aircraft Selection Menu or starts a new flight. We are working on a solution for this.

For 3rd-party developers, we have also added a new SimVar MOTION_SIMULATION (type: bool), which indicates whether motion simulation for the user aircraft is active.

All these changes will be delivered with SU5, version 1.7.10 (coming soon).

We appreciate your thorough testing of this change and would welcome feedback on any potential downsides.

Best regards,
Andrey/Asobo

2 Likes
11

Thank you very much indeed, sir!

I did another test (I repeated the previous one).

When I switch between helicopters, only the FFB joystick reacts to this (in my FFB profile has a shaker setting - vibration response due the engine RPM, and when I change the aircraft, part of the telemetry still affects the joystick, but not the DOF platform).

My platform is completely quite and moveless until the aircraft is going to airfield.

I want to thank you again, mister Pietrovitch!

1 Like
12

Hello @upisonup

This was fixed with SU5 Beta 1.7.11.0.
Let us know if this all good for you.

Regards,
Sylvain

1 Like
13

The product in which I came over this bug is not under active development anymore (to my knowledge).

As there was no response from dev team after we reported this bug the workaround to mitigate this was applied at our side. It could occasionally disable telemetry processing but was better than randomly kicking our customers.

So, this issue was resolved for us last 18 months, despite no action taken from MSFS side.

14

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.