[Godot v4.4] Gizmos exponentially increasing Draw Calls and Objects when turned on

[BryantCrisos]

Tested versions

• Reproducible in: v4.4-stable
• Not reproducible in: v4.3-stable

System information

Windows 10 - Godot_v4.4-stable_mono_win64 - Vulkin (Forward+) - NVIDIA GeForce GTX 1070 - Intel(R) Core(TM) i7-6800k CPU @ 3.40GHz (12CPUs), ~3.4GHz

Issue description

This issue was submitted before for 3.3.2 #49820

When having gizmos on in v4.4 the scene gets significantly slower with a huge increase in Objects and Draw Calls.
The Gif below shows the difference in Draw Calls and Objects compared to 4.3 when nodes are turned on.

v4.4 Object & Draw Calls when toggling Gizmos

v4.3 Object & Draw Calls when toggling Gizmos

Steps to reproduce

• Enable View frame and View Information
• Turn off View Gizmo, View Transform Gizmo, and View Grid
• Then them back on to see the difference in Draw calls and objects

Minimal reproduction project (MRP)

The project I used to replicate this issue is here:
https://github.com/Jamsers/Crater-Province-Level

[runzh-crypto]

I looked into this issue. I believe the thing we need to resolve is the **performance in viewing gizmos **
The information should be correct

The huge increase in Objects and Draw Calls is intended (correct me if I am wrong)
It was introduced for resolving this issue #95640

If you use MRP to compare the Objects and Draw Calls in both Forward+ and Mobile with view Gizmos on, you can see the numbers are very close

Forward+

Mobile

[lazarosY]

It seems the issue is unassigned, I am a rookie at this but I would greatly appreciate if you'd let me look into this issue!

[Zireael07]

@lazarosY Godot does not practice assigning issues. Just go ahead and look

[msmith-codes]

I will also take a look into this issue.

[lazarosY]

Update: I have noticed that it just so happens that after replicating the issue myself I was locked at the same framerate of 30 fps while having wildly different specs (6900xt 5700x). Have tried uncapping the frame-rate without much success, will keep investigating the issue.

[msmith-codes]

@lazarosY I haven't had a ton of time to look into this issue, but thanks for updating. Does it lock the framerate on 4.3 too or is that exclusive to 4.4?

[gagem-sigsev]

I will take a look as well.

[lazarosY]

@lazarosY I haven't had a ton of time to look into this issue, but thanks for updating. Does it lock the framerate on 4.3 too or is that exclusive to 4.4?

Hey there, no worries, it seems to be exclusive to 4.4, haven't checked the project on 4.3 though so it might be different, I will check that eventually but since it seems to be a legitimate issue I have been a bit preoccupied to fixing it on present versions. Please do provide an update if your findings match mine or if you have any updates, would be greatly appreciated!