Microsoft Animals will not move if created and instructed through SimConnect

Version: 1.6.33.0

SDK Version: 1.4.5

Frequency: Consistently

Severity: Blocker
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)

Marketplace package name: n/a

Context: Any Microsoft Animal package I have tested so far

Similar MSFS 2020 issue: not aware of an available issue

Bug description: I use the following code to move animals in the sim:

            _log.Debug($"Set object movement {objectId}");
            var waypointsArray = waypoints.Select(w => new SIMCONNECT_DATA_WAYPOINT()
            {
                Flags = (uint)SIMCONNECT_WAYPOINT_FLAGS.ON_GROUND | (uint)SIMCONNECT_WAYPOINT_FLAGS.SPEED_REQUESTED,
                ktsSpeed = w.Speed,
                Latitude = w.Location.Latitude,
                Longitude= w.Location.Longitude
            }).ToArray();
            var data = new Object[waypointsArray.Length];
            waypointsArray.CopyTo(data, 0);
            _simConnect?.SetDataOnSimObject(DataDefinition.SIMOBJECT_MOVE_DATA, objectId, SIMCONNECT_DATA_SET_FLAG.DEFAULT, data);

If I use this to move a BlackBear (Asobo animal) then this code works as expected. If I use this exact same code to move, for example, a OHemionusFemale (Microsoft animal), the animal does not move.

If needed I can provide more code and explanation.

Repro steps:

  1. Create the OHemionusFemale on a known location that you can observe
  2. Assign waypoints to the object to make it move

Attachments:

Private attachments:

Confirm, they don’t move
Pretty sure that you at least need to set some other variables (look at their animations XML, there are several non documented A VARS)

Take the opportunity to have a confirmation from Asobo that we can NOT reference the new Animals in our products (there is a reference about this in the Markeplace Agreement)
Asking if it is valid for Marketplace products only?
or there is a licensing issue with those asset and can’t be used in any paid product or only bt Microsoft of whatever.

In this case wouldn’t it be better to hardcode them so their are unavailable at all in the editors?

Thanks :folded_hands:

Thank you for your response. I downloaded the package for OHemionusFemale and checked out the animation xml in the package.

I found these variables are used:

  • FAUNA HEADING ROTATION ANGLE
  • FAUNA TURN RATE
  • FAUNA FORCE MAGNITUDE
  • FAUNA BEHAVIOUR STATE

FAUNA BEHAVIOUR STATE looked the most promising to me, so I tried adding it to a data definition to enable me to set it through SimConnect. This throws an exception EXCEPTION_NAME_UNRECOGNIZED.

It would seem that none of these variables can be set through SimConnect.

I have been playing with SimVarWatcher a bit and I found the same variables in there. These are not documented in the SDK documentation, nor can I find anything anywhere else.

FAUNA BEHAVIOUR STATE is an enum. I’ll try and tinker with it, but it would be so much better if some documentation would exist or if someone with knowledge about these variables could help out.

For right now the bug remains, because it is not proven that you can make these animals move by setting these variables.

I can now confirm that FAUNA BEHAVIOUR STATE can be added to a data definition. The type indeed has to be Enum with int32. I have not yet had the chance to try and set a new value.

Hello @mrjvdveen82

The AIObjectsAndWaypoints SimConnect SDK sample presents the same issue, so we’ll make sure this is looked at and the documentation for the missing fauna simvars is added.

Regarding the editorial aspect of this, I will seek clarification but for now I would advise against using any of the fauna simobjects from the Microsoft packages, and rather using your own, regardless of the platform you distribute your packages through.

Regards,
Sylvain

1 Like

Hello @FlyingRaccoon,

Thanks for your response! I’ll be looking forward to any updates on this issue.

Regards,

Jonathan