The Issue At Hand
Okay so I've just basically started with Godot 4.x, coming from 3.5. And in every project I've made, I always add a debug overlay in my projects to monitor performance. But something's wrong: no matter what I do (change code, remove packed scenes or objects, disable vsync, change max_fps), the framerate hits the peak it can make in the first couple seconds, then dips down ALL the way to 60, despite me having a 144Hz monitor.

Maybe I'm missing something really obvious here, but I have never had this problem in any of my 3.5 projects. If someone could help me fix (or at the very least understand) this issue, I'd be extremely grateful : )

(Edit: some additional context. this happens regardless of scene "complexity", and I say that ironically because I usually just have a simple 3D prototype scene running)

    • Edited

    CreatureComforts the framerate hits the peak it can make in the first couple seconds, then dips down ALL the way to 60, despite me having a 144Hz monitor.

    Interesting. Well, Godot 4 can certainly display more than 60 fps all the time. (I have a 240Hz monitor.)

    The monitor counter roughly matches the frame rate of this scene:

    Have you checked the latest version of the engine? Do you have G-SYNC or analog enabled?

      CreatureComforts disabling VSYNC in godot should probably unlock the FPS.
      VSYNC could be forcibly enabled somewhere else. like, NVIDIA used to have these programs that overrid graphics settings, including VSYNC.

        Jesusemora I've tried Vsync on and off, as I explained in my original post and it doesn't change anything. Same thing when I force Vsync through Nvidia's control panel. Nothing I have tried in the editor or with my graphics card software changes it unfortunately :/

        • xyz replied to this.

          Tomcat I use the Steam release for 4.X versions, so it always updates it when they're released there, currently it's 4.2.1. Running a 3050 Ti in my computer and Nvidia doesn't give me G-SYNC options for some reason, so I couldn't change those even if I wanted to lmao

            xyz Yeah, I've done that and the Process time seems a bit high, but I've tried editing my code a bunch as previously mentioned and to no avail. So I don't exactly know what I'm doing wrong here lol

            CreatureComforts Just wanna add to this that this problem isn't limited to my current project, it happens in my other 4.X projects too.

            Tomcat Every other mode than Unshaded is 60, tho Unshaded still only has me at like 120-ish (chalk it up to the rather low 4GB VRAM ig)

            (Edit: I changed some settings to max out performance)

            xyz Process Time starts low then just jumps to ~ 16ms.

            • xyz replied to this.
              • Edited

              CreatureComforts The profiler should give you a list of things that consume the frame time, if you know how to read and interpret its outputs. Identify the worst offenders and try to deal with them.

              Also, make a MRP and post it for other people to test it, to see if the problem persists across multiple configurations or just appears on your specific hardware setup.

                8 days later

                xyz okay i ended up finding out the issue, it was a weird artifact of having windows open on my other connected screen lmao. problem solved 🙂