Problems with bounding boxes and animation mixing

[DylanRJohnston]

I've been encountering a weird issue where at certain camera angles portions of the mesh of a blueprinted entity are culled.

Enabling AABB gizmos shows a bunch of bounding boxes floating off in space.

Inspecting the original model, and the one exported from blender show large differences in their reported bounding boxes and the animations from the different models are getting all mixed in together.

Perhaps I'm doing something catastrophically incorrect with the way I've setup my blender project but I've followed the video guides closely and can't figure out what I'm doing incorrectly.

[DylanRJohnston]

Copying the original glb file over the exported one in the library folder results in the correctly placed bounding boxes.

[DylanRJohnston]

This seems to be a related issue experienced by the three.js community mrdoob/three.js#14499

[DylanRJohnston]

The animation mixing is still a problem, but I was able to solve the problem with the bounding boxes bevyengine/bevy#11131. It appears to be an issue with bevy's handling of gltf skinned meshes.

[kaosat-dev]

Hi @DylanRJohnston !
If I understand correctly :

• the issue with bounding boxes is fixed by the fix in the thread on the Bevy github you linked to ?
• the issue with animations is they get attached to the wrong model/blueprint or do all models have all animations from all other models ?

There is a HUGE pr that I hope to release this week that fixes a ton of issues with animations & changes the way animations are "attached" to blueprints, so I hope that will fix this issue as well.
The PR on the Blender side is not quite consumption ready , but I'll ping you once it is.