Severity: *Low
(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: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description:
The SDK documentation suggests that if you do not have any seat logic objects you use:
SEAT_DEFAULT_Pilot and the pos parameter (not recommended). I assume not recommended at least works to some degree. However it does not work at all for me.
The pilot is ALWAYS positioned at 0,0,0.
The gizmo for position does not show.
The rotation gizmo does not show.
The pos parameter is added to the navigation_graph_pilot, but has no effect.
My blend file has a node pilot_0 positioned on the seat as was the required position for 2020. Moving to feet does nothing also.
However I cannot move the gizmo by grabbing the x,y,z arrows. like I can with the other navigation graph nodes. If I manually type in the pos x,y,z the pilot goes to the correct position. PILOT_0 model node does nothing. PILOT_ST10 node name stays at 0,0,0 with the position set to -1,-1.-4.
Unless I missed something in your bug report, you should use the position only when no Model Node is provided.
The Model Node is intended to place the pilot precisely, based on where you want their feet to be.
The gizmo is disabled when the Model Node input is filled.
The position is not supposed to work when a ModelNode is referenced, which is why the gizmo does not appear.
You can use either one but not both otherwise it could lead to weird behavior..
It is not a critical feature, just that this one node does not work the same as the other pilot nodes, in that the gizmo cannot be used to set the position. The dev needs to manually type in and guessed at. And this is just for the one case of using the SEAT_ DEFAULT_PILOT.
I am trying to explain how to build an aircraft in my tutorials, and am at the part, where you go from a 2020 pilot setup to a 2024 setup, the first step using the SEAT_DEFAULT_PILOT.
Just to point out another PILOT issue - Multiplayer is affected as reported to me. There is a pilot generated where it should not be. Looks like at 0,0,0
