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
i'm writing another demo with troisjs recently with three.sprite(not using trois sprite component because the sprite is not supported while coding this demo lol) & scene and i find out that $refs.sceneInstance.remove doesnt work. i've checked the sprites' parent is the scene's reference and $refs.sceneInstance.scene.remove doesn't work as well(but .add() api works fine ,curious)
`
//so this part of code do not work
// debugger;
// activatedNodeInstanceList.forEach(node=>{
// this.$refs.sceneInstance.remove(node);
// })
debugger;
//directly use removeFromParent api works fine
activatedNodeInstanceList.forEach(node=>{
node.removeFromParent();
})
`
trois version:0.3.2 three:0.129.0 original src code file
besides i see the doc installation is still using ^0.127 which is not support the removeFromParent api , but i check the trois Object3D sourcecode to find out it has already supported removeFromParent api :P
The text was updated successfully, but these errors were encountered:
i'm writing another demo with troisjs recently with three.sprite(not using trois sprite component because the sprite is not supported while coding this demo lol) & scene and i find out that $refs.sceneInstance.remove doesnt work. i've checked the sprites' parent is the scene's reference and $refs.sceneInstance.scene.remove doesn't work as well(but .add() api works fine ,curious)
`
//so this part of code do not work
// debugger;
// activatedNodeInstanceList.forEach(node=>{
// this.$refs.sceneInstance.remove(node);
// })
`
trois version:0.3.2 three:0.129.0
original src code file
besides i see the doc installation is still using ^0.127 which is not support the removeFromParent api , but i check the trois Object3D sourcecode to find out it has already supported removeFromParent api :P
The text was updated successfully, but these errors were encountered: