Maniphest T80460

gltf / glb-export: 2nd level hierarchy selections can't be exported
Closed, ResolvedKNOWN ISSUE
Actions

Assigned To
Julien DUROURE (julien)
Authored By
Christoph Werner (Taros)
Sep 4 2020, 10:00 AM
Tags
  • Add-ons (Community)
Subscribers
Christoph Werner (Taros)
Julien DUROURE (julien)
Philipp Oeser (lichtwerk)
Tokens
"Love" token, awarded by Leroy."Burninate" token, awarded by Taros.

Description

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

  1. Open my example .blend file and select "root_torus" empty and its sub objects
  2. 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.blend700 KBDownload

Related Objects

Mentioned Here
rBA33eae7da675d: glTF exporter: filtering of exported nodes
rB0330d1af29c0: Fix T77900: File Browser in macOS fullscreen crashes

Event Timeline

Christoph Werner (Taros) created this task.Sep 4 2020, 10:00 AM
Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Confirmed.Sep 4 2020, 10:58 AM
Philipp Oeser (lichtwerk) changed the subtype of this task from "Report" to "Bug".
Philipp Oeser (lichtwerk) added subscribers: Julien DUROURE (julien), Philipp Oeser (lichtwerk).

Can confirm.

@Julien DUROURE (julien) : this is not a known limitation, is it?

Julien DUROURE (julien) changed the subtype of this task from "Bug" to "Known Issue".Sep 4 2020, 2:17 PM

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

Christoph Werner (Taros) added a comment.Sep 4 2020, 2:56 PM
In T80460#1009187, @Julien DUROURE (julien) 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.

Christoph Werner (Taros) awarded a token.Sep 4 2020, 6:13 PM
Leroy (Leroy) awarded a token.Sep 5 2020, 2:45 AM
Julien DUROURE (julien) added a comment.Sep 6 2020, 7:39 PM

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

Julien DUROURE (julien) closed this task as Resolved.Oct 21 2020, 4:28 PM
Julien DUROURE (julien) claimed this task.

This is now fixed after commit rBA33eae7da675d532bbb9c12b129c0e30228f5f000