gltf / glb-export: 2nd level hierarchy selections can't be exported #80460

Closed
opened 2020-09-04 10:00:11 +02:00 by Christoph Werner · 9 comments

System Information
Blender version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release
build date: 2020-08-31, 10:00:13
platform: Windows

renderer: 'GeForce GTX 1080 Ti/PCIe/SSE2'
version: '4.5.0 NVIDIA 442.59'

Short description of error

  • glb files are "empty" when trying to export 2nd level hierarchy object selections (See my screenshot below)
  • Happens in all Blender versions, that supports gltf / glb export (tried in 2.81+)

Exact steps for others to reproduce the error

  • Open my example .blend file and select "root_torus" empty and its sub objects
  • Export the selection as .glb file format
  • Results in an empty file when viewing it in a glb viewer. File was created, but no objects were exported.

Notes

  • If you select the whole "root_cube" hierarchy, then all objects will be exported.
  • To export the "root_torus" hierarchy only, you have to unparent it from "root_cube". Not a good solution.
  • Even single meshes in 2nd level hierarchies can't be exported and have to be moved to the scene root or to the parent root!

The problem: Only object hierarchies, that are in the scene root can be exported, sub hierarchies can't.

Expectation: Make it possible to export any single selected object or group selections, from any hierarchy location.

Example File and Screenshot
blb_export_bug01.blend
glb_export_hierarchy_bug01.jpg

**System Information** Blender version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release build date: 2020-08-31, 10:00:13 platform: Windows renderer: 'GeForce GTX 1080 Ti/PCIe/SSE2' version: '4.5.0 NVIDIA 442.59' **Short description of error** - glb files are "empty" when trying to export 2nd level hierarchy object selections (See my screenshot below) - Happens in all Blender versions, that supports gltf / glb export (tried in 2.81+) **Exact steps for others to reproduce the error** - Open my example .blend file and select "root_torus" empty and its sub objects - Export the selection as .glb file format - > Results in an empty file when viewing it in a glb viewer. File was created, but no objects were exported. **Notes** - If you select the whole "root_cube" hierarchy, then all objects will be exported. - To export the "root_torus" hierarchy only, you have to unparent it from "root_cube". Not a good solution. - Even single meshes in 2nd level hierarchies can't be exported and have to be moved to the scene root or to the parent root! The problem: Only object hierarchies, that are in the scene root can be exported, sub hierarchies can't. **Expectation:** Make it possible to export any single selected object or group selections, from any hierarchy location. **Example File and Screenshot** [blb_export_bug01.blend](https://archive.blender.org/developer/F8839317/blb_export_bug01.blend) ![glb_export_hierarchy_bug01.jpg](https://archive.blender.org/developer/F8839318/glb_export_hierarchy_bug01.jpg)

Added subscriber: @ChristophWerner

Added subscriber: @ChristophWerner
Member

Added subscribers: @JulienDuroure, @lichtwerk

Added subscribers: @JulienDuroure, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Can confirm.

@JulienDuroure : this is not a known limitation, is it?

Can confirm. @JulienDuroure : this is not a known limitation, is it?
Member

This is a known issue.
Root cause: We traverse the object tree from root objects. So traversing stops when find a not selected object. Other issue : only local matrix are exported, so starting not at root is not possible for now

Some tests are in progress to have a better solution. See discussion here : https://github.com/KhronosGroup/glTF-Blender-IO/pull/1126

This is a known issue. Root cause: We traverse the object tree from root objects. So traversing stops when find a not selected object. Other issue : only local matrix are exported, so starting not at root is not possible for now Some tests are in progress to have a better solution. See discussion here : https://github.com/KhronosGroup/glTF-Blender-IO/pull/1126

In #80460#1009187, @JulienDuroure wrote:
This is a known issue.
Root cause: We traverse the object tree from root objects. So traversing stops when find a not selected object. Other issue : only local matrix are exported, so starting not at root is not possible for now

Some tests are in progress to have a better solution. See discussion here : https://github.com/KhronosGroup/glTF-Blender-IO/pull/1126

So there is a chance this will be fixed sometime? Would be good for a fluent workflow.

> In #80460#1009187, @JulienDuroure wrote: > This is a known issue. > Root cause: We traverse the object tree from root objects. So traversing stops when find a not selected object. Other issue : only local matrix are exported, so starting not at root is not possible for now > > Some tests are in progress to have a better solution. See discussion here : https://github.com/KhronosGroup/glTF-Blender-IO/pull/1126 So there is a chance this will be fixed sometime? Would be good for a fluent workflow.
Member

Sure it will be fixed sometime. But not planned yet on short timeline.

Sure it will be fixed sometime. But not planned yet on short timeline.
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Julien Duroure self-assigned this 2020-10-21 16:28:26 +02:00
Member

This is now fixed after commit 33eae7da67

This is now fixed after commit 33eae7da67
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#80460
No description provided.