gltf export fail; parent_bone not being ignored when Parent Type is "Object" #104583

New Issue

Jonathan Mafi · 2023-05-01T23:52:15+02:00

Jonathan Mafi commented

2023-05-01 23:52:15 +02:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.41

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
Worked: (newest version of Blender that worked as expected)

Short description of error
When exporting gltf/glb there is an error if the Parent Type is Object but the parent_bone still has data on it.

Exact steps for others to reproduce the error

Attach geo to rig via armature modifier with the parent_bone set in background via any method. One method:
a) Parent geo to armature bone.
b) Change mind and decide you want to use skinning instead. So you parent with automatic weights and change Relations>ParentType to "Object".
c) bpy.data.objects["MyGeo"].parent_bone still has data
Now go to export a gltf and it will error as explained here:
https://github.com/KhronosGroup/glTF-Blender-IO/issues/1015
Unsure if this is a bug per se. However the expected behaviour is that now we have set Parent Type to Object either parent_bone should reset (Blender side) OR the gltf exporter should ignore parent_bone? (gltf addon side).

Quick fix is manual update
Or if in a studio pipeline is set this to empty string
bpy.data.objects["Cube"].parent_bone = ""

However as mentioned Parent Type is object so parent_bone should be ignored imo. And one wont always know if its empty or not.

System Information Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.41 Blender Version Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7 Worked: (newest version of Blender that worked as expected) Short description of error When exporting gltf/glb there is an error if the Parent Type is Object but the parent_bone still has data on it. Exact steps for others to reproduce the error Attach geo to rig via armature modifier with the parent_bone set in background via any method. One method: a) Parent geo to armature bone. b) Change mind and decide you want to use skinning instead. So you parent with automatic weights and change Relations>ParentType to "Object". c) bpy.data.objects["MyGeo"].parent_bone still has data Now go to export a gltf and it will error as explained here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1015 Unsure if this is a bug per se. However the expected behaviour is that now we have set Parent Type to Object either parent_bone should reset (Blender side) OR the gltf exporter should ignore parent_bone? (gltf addon side). Quick fix is manual update Or if in a studio pipeline is set this to empty string bpy.data.objects["Cube"].parent_bone = "" However as mentioned Parent Type is object so parent_bone should be ignored imo. And one wont always know if its empty or not.

example_hiddenBoneParentType.blend

830 KiB

Jonathan Mafi added the

labels 2023-05-01 23:52:16 +02:00

Julien Duroure commented

2023-05-02 04:16:20 +02:00