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
Seems totally broken, looks like the materials are getting imported but assigned to the wrong submesh. Used to work, so need to work out what broke it.
Also need to do something to deal with the .mesh.json thing that the new exporter does, as it does it on multimesh exports.
Need to have a think about how to handle multimesh exports, as dont need/want to import the seperate meshes as well as the merged bits if they've been done that way.
The text was updated successfully, but these errors were encountered:
By multimesh import, do you mean just importing a mesh which was exported from Wolvenkit with multimesh or selecting multiple meshes at once on glb import? Does it still work as expected on the lts version?
Seems totally broken, looks like the materials are getting imported but assigned to the wrong submesh. Used to work, so need to work out what broke it.
Also need to do something to deal with the .mesh.json thing that the new exporter does, as it does it on multimesh exports.
Need to have a think about how to handle multimesh exports, as dont need/want to import the seperate meshes as well as the merged bits if they've been done that way.
The text was updated successfully, but these errors were encountered: