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 have a bunch of nodes inside gltf which i enable or disable based on the player condition. like only show a object if player has special goggles equipped or don't show an object if player has already collected it etc..
I tried looking through docs (and examples) and cannot find anything to help with this. I am just learning this stuff, so i might have missed an obvious method to do this. I have seen some comments that you need the object handle to keep the object alive, but idk how i would revive that object later when it needs to respawn.
On matrix, i was told to use the nodes local_transform attribute to move it out of camera space as a workaround. but the node itself might have a transform of its own, and i would be over writing it.
was hoping that there would be a simple method to select which objects to skip rendering. and re-enable them later.
The text was updated successfully, but these errors were encountered:
I have a bunch of nodes inside gltf which i enable or disable based on the player condition. like only show a object if player has special goggles equipped or don't show an object if player has already collected it etc..
I tried looking through docs (and examples) and cannot find anything to help with this. I am just learning this stuff, so i might have missed an obvious method to do this. I have seen some comments that you need the object handle to keep the object alive, but idk how i would revive that object later when it needs to respawn.
On matrix, i was told to use the nodes local_transform attribute to move it out of camera space as a workaround. but the node itself might have a transform of its own, and i would be over writing it.
was hoping that there would be a simple method to select which objects to skip rendering. and re-enable them later.
The text was updated successfully, but these errors were encountered: