SimVar "SIM SHOULD SET ON GROUND" is not recognized, "SIM ON GROUND" has no effect

Version: ‘SunRise’ version 12.2 (build 282174.999) using SimConnect version 12.2 (build 0.0)

SDK version: 1.5.3

Frequency: Consistently

Severity: High

Marketplace package name: N/A

Context: N/A

Similar MSFS 2020 issue: Not tested

Bug description:

The documentation states a SimVar named “SIM SHOULD SET ON GROUND" is available that is settable, whereas “SIM ON GROUND" is marked as read-only. However, any attempt to use the former will result in a “SIMCONNECT_EXCEPTION_NAME_UNRECOGNIZED" message being returned. Calling SimConnect_SetDataOnSimObject with “SIM ON GROUND" will not cause any exception to be returned, but also not correct the aircraft to be properly on the ground.

Note: I am aware there is another bug report that might be an alternate description of the issue of e.g. a default DA62 being created with the wheels halfway underground even if “SIM ON GROUND" is set to 1, but the unknown SimVar is still a bug. Maybe the first should be removed from the docs and the other marked as settable?

Repro steps:

See example 7-2 here.

Attachments: N/A

Private attachments: N/A

Hello @BenkeiBuddy

From what I can see in the code, it’s not settable.
This looks like a legacy variable and I’m not sure it fills a role in the modern sim.
I’ll have that reviewed.

Regards,
Sylvain

1 Like

Hello @BenkeiBuddy

This is just a flag variable, used internally and set to true for a frame before the aircraft is moved to ground.
You should use IS ON GROUND for reading.
Regarding how to set the aircraft position, this should rather be done through SimConnect using the SIMCONNECT_DATA_INITPOSITION structure.

Documentation was updated accordingly.

Regards,
Sylvain

Ok, thank you

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.