- Toulouse, France
- https://julienduroure.com
- Joined on
2010-10-18
Hello, As described by Brad, I confirm (as the main glTF I/O dev) that having access by python to segment matrices and weights will be very useful. We will be able to convert it on the fly to…
At short term, I added a check to avoid crash at glTF export
@lichtwerk Regarding glTF exporter: should I add a check to avoid crash, or should I consider that there can't be any name collision, and any collision is a Blender (core) bug?
Hello, This bug is already fixed in 3.5 and newer. We can close this ticket
This ticket can be closed, but because we are not on blender-addons repo, I don't have the necessary rights.
@Bachelier-Baptiste Not sure what you are using for exporting or converting your file into glTF, but you should report this bug to the corresponding team, as the glTF is not valid
The glTF validator says this file is not compliant with the glTF specification https://github.khronos.org/glTF-Validator/
Even if…
Hello, Confirmed on 3.4, but this bug is already fixed in 3.5 and newer. See bddbd5ed5fa6af76b50b4f9ac202cc2903977248 Closing this ticket.
action.frame_range
span always >=1 when there's only 1 key frame in it.
Agree with that!
The glTF code (because I first report it because I discovered it debugging a glTF bug) has now a workaround ( using python fcurve.range() that returns the actual range values)…
action.frame_range
span always >=1 when there's only 1 key frame in it.
Additional information: bpy.context.object.animation_data.action.fcurves[0].range() returns the right result (6.0, 6.0)
Fixed by blender/blender-addons@6ac724926a I can not close this ticket because it was created on blender repo, not blender-addons Can someone close it?