Bug: v8.0.0-rc.5 Culled containers are culled forever about pixijs

[davidye]

@Zyie @GoodBoyDigital

One thought I had was that the visible property is being overloaded. Perhaps there should be a separate culled property that is independent of visible.

For example I may want to mark a node with visible = false and that toggles in response to user input. With this implementation of culling, which uses visible directly, I would need to explicitly set node.visible = true / false before every call to Culler.shared.cull().

Culling should probably not overwrite visible in this way because it's more of an optimization detail that changes from render() to render(), not a state of the node?

[Zyie]

hey @davidye i've added a pr to add a new property so it no longer overrides visible. Let me know if this solves your issues

[davidye]

@Zyie 🙏 thank you! Will test once the new rc is published.

[davidye]

Working great now, thank you!