GLTF 2.0 export includes hidden armatures in disabled collections #87093

New Issue

Casey · 2021-03-31T18:15:24+02:00

Casey commented

2021-03-31 18:15:24 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: blender/blender@02948a2cab
Worked: (newest version of Blender that worked as expected)

Addon Information
Name: glTF 2.0 format (1, 6, 8)
Author: Julien Duroure, Scurest, Norbert Nopper, Urs Hanselmann, Moritz Becher, Benjamin Schmithüsen, Jim Eckerlein, and many external contributors

Short description of error
Exporting GLTF of a scene with "only selected" active will still export armatures in the scene even if they're unselected and in disabled collections. We noticed this after importing our scenes into Babylon .js and almost a hundred rigs from other (disabled) collections were coming with.

Exact steps for others to reproduce the error

Place armatures in a disabled collection.
Make some geometry in the main scene collection.
Select the geometry in the main scene collection,
go to export to GLTF 2.0 and tick "only selected".
Export and re-import again.
The armatures in the disabled collection will come with.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `blender/blender@02948a2cab` Worked: (newest version of Blender that worked as expected) **Addon Information** Name: glTF 2.0 format (1, 6, 8) Author: Julien Duroure, Scurest, Norbert Nopper, Urs Hanselmann, Moritz Becher, Benjamin Schmithüsen, Jim Eckerlein, and many external contributors **Short description of error** Exporting GLTF of a scene with "only selected" active will still export armatures in the scene even if they're unselected and in disabled collections. We noticed this after importing our scenes into Babylon .js and almost a hundred rigs from other (disabled) collections were coming with. **Exact steps for others to reproduce the error** - Place armatures in a disabled collection. - Make some geometry in the main scene collection. - Select the geometry in the main scene collection, - go to export to GLTF 2.0 and tick "only selected". - Export and re-import again. The armatures in the disabled collection will come with.

Casey commented

2021-03-31 18:15:24 +02:00

Added subscriber: @Casey-3

Germano Cavalcante commented

2021-04-01 23:56:45 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-04-01 23:56:45 +02:00

The glTF 2.0 addon has its own tracker for issues:
https://github.com/KhronosGroup/glTF-Blender-IO/issues/

I suggest checking if this issue has already been reported there.

The glTF 2.0 addon has its own tracker for issues: https://github.com/KhronosGroup/glTF-Blender-IO/issues/ I suggest checking if this issue has already been reported there.

Casey commented

2021-04-02 00:10:25 +02:00

I took a look, it looks like there's still open tickets about it so I guess that's it. It's just not fixed yet