-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with InstancedMesh after phy.remove #26
Comments
i will look but i+=2 seems wrong ? |
It's meant to illustrate there is an issue if you remove some of them, not just the first or last added. |
i see yes, i have to find better method without id |
ok remove on instance should be fixed. |
I'm still seeing problems when I use instance. |
do you readd object on same instrance ? |
I see that's the problem, I wasn't giving them a name. The only reason I'd say this is still a bug is because it works correctly when instance is not specified. |
I've just noticed that if I also add other objects that have a different mesh and are not using an instance, these flicker and disappear / swap places. |
Create some objects that make use of InstancedMesh
Then remove some.
The mesh of the removed objects remains in view.
I've also seen an issue where the remaining instances then flicker in and out of view.
The text was updated successfully, but these errors were encountered: