Snowdrama / is on Nostr

Video game nomad, I go where there are games to play!

https://linktr.ee/snowdrama

Indie Dev, Streamer, YouTuber.

Currently Playing: Star Ocean the Divine Force
Next Game: Going back to finish Tales of Arise

Last Notes

2024-07-10 11:31:38

- reply

Yep exactly, it's essentially the active state in Unity. It also has lifecycle callbacks similar to OnEnable/OnDisable -> _node_active/_node_inactive
I could see not needing it until the project is bigger so I wouldn't blame you either, I was just kind of surprised when I found out this wasn't in Godot already haha

2024-07-10 09:05:34

- reply

The original author's use case was to remove sections of their game from affecting the world, including the collision and everything, without having to delete the node from the scene, or manually disable process_mode on every child.
My use tends to be more for things like simplifying object pooling, and initialization for editor tools.

2024-07-10 08:57:03

- reply

The problem with Show/Hide is that it's only affecting visibility. In complex games we often want to fully cull objects.
Scripts eat up performance even if the result isn't visible, hidden objects still have collisions that can produce user bug reports, and areas can still detect things like triggering cutscenes unintentionally.
Fully disabling the node stops all of that.

2024-07-10 06:48:54

This is going to be a huge improvement to people's workflows I believe!
I've been chatting with the people over on the Godot github about this feature!
It lets you with a single option, toggle visibility, process mode, toggle collisions, and toggle accepting signals!
It has lifecycle methods for when it becomes active or inactive, super useful for so many reasons!
#godot #godotengine #Godot4
https://github.com/godotengine/godot/pull/94144
https://cdn.masto.host/mastodongamedevplace/media_attachments/files/112/760/859/537/593/156/original/8f7097a67f455043.png