- Toulouse, France
- https://julienduroure.com
- Joined on
2010-10-18
So ... If this is not a bug in glTF neither in FBX (but some feature request), I think we can close this ticket
Hello, Agree with Scurest analysis. Blender is not a glTF editor, but uses importer / exporter. Even if we try to avoid it, we sometimes need to change / convert / adapt the content of glTF…
Hello, This should already fixed here: dbc8b295195aec360a127465e90fba8e97c9ba60
This will probably goes to 4.3.1 when released Closing this ticket, as already solved
Hello, More than a week without any answer, closing this ticket
Feel free to comment again to give the requested information
@mont29 Do you want me to merge the PR, or do you? Or should we wait Campbell's feedback about your other remarks? (Do you have any idea about when the 4.3.1 (if any) will be planned?)
This is a regression in a0f653c0022c94461ef8c34816c1334ee74add7f PR in progress
Note:
Worked: 4.2.3
Draco in bpy as a module didn't exist yet in 4.2. This is a new feature of 4.3
This is probably a Windows only issue, because of this:
c57ebc99eb/scripts/addons_core/io_scene_gltf2/io/com/d
…
Seems we will have to add a fix for Draco library. Investigation in progress (Windows only issue?)
The A B or C (line or block) are written in comment in the code Ticket was discussed during the Animation & Rigging module meeting today
OKi, thanx. These commits are in main though if you do a merge, no?
Yes, you are right. Having a note to explicitly say it will avoid someone else (or my future me) to do the same error…