Open
Description
On my Windows 10 machine with an Nvidia card, setting r_swapInterval
caps the FPS as expected, for values -4 to -1 or 1 to 4. But despite the lower FPS, it increases the CPU usage. I did some tests with the 0.54.1 release with all default cvars except resolution and full screen, looking at the plat23 alien base. At 125 FPS without vsync, the CPU usage is 5%. With any value of vsync enabled (which gives possible FPSes of 60, 30, 20, or 15), the CPU usage is 8%. This means roughly all of 1 core, as the denominator here is 12 cores.
The problem does not occur with Intel graphics.
The problem does not occur in the main menu. So it can't be explained by something as simple as always busy-looping until the monitor is ready...