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
{{ message }}
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.
I create a texture that's shared between different objects that dynamically get created and destroyed. When the last object using a texture gets destroyed, the texture is deleted. So that when I create the next object that wants to use the texture, I get an error.
My workaround is to create materials together with the textures (that are never used), this keeps the textures alive. But I think that it's at least surprising if not an outright bug that a texture gets deleted while I have a reference to it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I create a texture that's shared between different objects that dynamically get created and destroyed. When the last object using a texture gets destroyed, the texture is deleted. So that when I create the next object that wants to use the texture, I get an error.
My workaround is to create materials together with the textures (that are never used), this keeps the textures alive. But I think that it's at least surprising if not an outright bug that a texture gets deleted while I have a reference to it.
The text was updated successfully, but these errors were encountered: