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
"Instance" command seems to delete meshes sometimes where post optimization the instanced assets will disappear from the model. The file in question works with gltf.report but not with gltf-transform being used in three.js via WebIO. It's strange because other assets coming from Blender seem to be fine and utilize mesh_gpu_instancing correctly. This particular asset was generated with Unreal, perhaps something in their node hierarchy is messing things up. I've provided a link to the asset below. Removing Instance() from my code has the asset appear correctly.
Tested this with the CLI and got the same result, might have something to do with 'meshopt' and the other transforms happening in the same document.
kitaedesigns
changed the title
"Instance" command seems to accidentally delete instanced meshes when used with NodeJS and ThreeJS
"Instance" plus "meshopt" seems to accidentally delete instanced meshes when used with NodeJS and ThreeJS
Dec 13, 2024
"Instance" command seems to delete meshes sometimes where post optimization the instanced assets will disappear from the model. The file in question works with gltf.report but not with gltf-transform being used in three.js via WebIO. It's strange because other assets coming from Blender seem to be fine and utilize mesh_gpu_instancing correctly. This particular asset was generated with Unreal, perhaps something in their node hierarchy is messing things up. I've provided a link to the asset below. Removing Instance() from my code has the asset appear correctly.
ASSET
https://www.dropbox.com/scl/fi/fxv1ipfo9ujwgqjim3odf/TrackerlessStudio.glb?rlkey=2uerxpwfzxw8equyqorauxi1d&st=fih69joj&dl=0
CODE
The text was updated successfully, but these errors were encountered: