OS/device including version:
Ubuntu Linux 20.04 / GLES3 renderer
Issue description:
When filling a meshlib using the "Import from Scene" command from the "Mesh Library" editor menu, the collision shapes' transformation is not respected. The resulting shapes attached to the items in the meshlib are snapped back to the origin.
This issue does not happen when doing it from the scene by using the "Convert to... Mesh Library" function.
Example screenshot with a mesh that uses a CollisionShape of type "BoxShape" moved up to position [0,2,0] using both methods:
Steps to reproduce:
Create a scene to be used as a source for the meshlib:
MeshInstance.Mesh -> New CubeMesh (with default dimensions)
CollisionShape.Shape -> New BoxShape (with default dimensions)
Set CollisionShape.Transform.Translation to [x=0, y=2; z=0]
Save scene
Create meshlib
Invoke "Mesh Library -> Import from Scene" on new meshlib, and select previously saved scene
When using the meshlib in a gridmap, you'll notice that the CollisionShape of the mesh snapped back to [0,0,0], and thus not respecting the transformation from the original scene file.
Expectation:
The CollisionShape of the mesh should be at [0,2,0]
Godot version: 3.2.4.beta6 3.2.4.rc1
OS/device including version: Ubuntu Linux 20.04 / GLES3 renderer
Issue description: When filling a meshlib using the "Import from Scene" command from the "Mesh Library" editor menu, the collision shapes' transformation is not respected. The resulting shapes attached to the items in the meshlib are snapped back to the origin. This issue does not happen when doing it from the scene by using the "Convert to... Mesh Library" function.
Example screenshot with a mesh that uses a CollisionShape of type "BoxShape" moved up to position [0,2,0] using both methods:
Steps to reproduce:
When using the meshlib in a gridmap, you'll notice that the CollisionShape of the mesh snapped back to [0,0,0], and thus not respecting the transformation from the original scene file.
Expectation: The CollisionShape of the mesh should be at [0,2,0]
Minimal reproduction project: sample_project_3.2.4.rc1.zip
I hope I could make clear what the issue is. The problem does not occur in 3.2.4.beta4 + 3.2.4.beta5.