Can you tell me if the camera node uses an improves rendering performance by processing and rendering only the objects within the camera's field of view, defined by its frustum while excluding those outside this view from the rendering pipeline?
See this webpage:

  • xyz replied to this.

  • catafest Godot already does it. You likely won't get any benefits by implementing your own on top of it.
    Note that this doesn't include processing, only rendering. Node's process will run regardless if it was culled or not. So if it fits your case, you can benefit from toggling processing depending on visibility. However, no need to make your custom frustum checking function as Godot already has VisibleOnScreenNotifierXD

      • xyz

      • Post #2

      catafest Of course it does. Frustum culling is a fundamental optimization technique. It's decades old. Every renderer worth its salt is using it.

          xyz then Godot already has this optimization, starting with basic rendering software ... but can I implement a similar management of objects to improve it more - this is the main idea, or will be the same?.. can I start a benchmark test project, but I ask first here

          • xyz replied to this.

              • xyz

              • Post #4
              • Edited
              • Best Answerset by catafest

              catafest Godot already does it. You likely won't get any benefits by implementing your own on top of it.
              Note that this doesn't include processing, only rendering. Node's process will run regardless if it was culled or not. So if it fits your case, you can benefit from toggling processing depending on visibility. However, no need to make your custom frustum checking function as Godot already has VisibleOnScreenNotifierXD

                That is a good answer to this question. I don't test this function but it can help me.