You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for this great tool! I'm opening this issue because I obtained a weird result while decomposing some obj meshes:
When specifying the --save-mtl flag, the materials associated to each mesh are switched (eg if I split base.obj into base_0.obj and base_1.obj, the material for base_0.obj will be associated to base_1.obj and vice versa). Have you ever reproduced that behavior?
My guess is that the declaration order of the textures in the original mtl file will influence that?
The text was updated successfully, but these errors were encountered:
Thank you for this great tool! I'm opening this issue because I obtained a weird result while decomposing some obj meshes:
When specifying the
--save-mtl
flag, the materials associated to each mesh are switched (eg if I splitbase.obj
intobase_0.obj
andbase_1.obj
, the material forbase_0.obj
will be associated tobase_1.obj
and vice versa). Have you ever reproduced that behavior?My guess is that the declaration order of the textures in the original mtl file will influence that?
The text was updated successfully, but these errors were encountered: