Settings The R&D facility scene does not appear to honor v-sync [possibly a Wine/Linux issue]

[krbvax]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Wine 9.0-rc3 on Linux | CPU: AMD Ryzen 7 | GPU: NVIDIA 3060 Ti | RAM: 32GB

 

The R&D facility scene does not appear to respect the v-sync option, creating much more GPU load than expected given the simplicity of the scene.

Steps to reproduce: (assuming a test system with a sufficiently powerful GPU relative to monitor frame rate)

1. Ensure that the V-Sync option in Settings/Graphics is set to "off".
2. Go to the title screen, and observe (such as by checking GPU power consumption) that GPU usage is high.
3. Change the V-Sync setting to "on".
4. Go to the title screen, and observe that GPU usage is lower than in step 2.
5. Create or load an Exploration campaign.
6. Enter the R&D facility.
7. Observe GPU usage.
8. Open the Settings menu and change the V-Sync setting to "off".
9. Observe GPU usage.

Expected behavior: GPU usage remains low in step 7 due to the low complexity of the scene, then increases in step 9 when V-Sync is disabled.

Observed behavior: GPU usage increases significantly in step 7 and does not change significantly in step 9.

[Anth]

@krbvax
Its working correctly on my system. (Windows 10)
Added that it might be Wine/Linux related to the title.

[krbvax]

Thanks for the prompt check.

I do recall that KSP1 (in that case, the native Linux version) had the same problem with R&D as well as similar 2D menu scenes (mission control, astronaut complex etc). Perhaps there was some Linux-incompatible v-sync method used in the code for those scenes which got carried over into KSP2? V-sync definitely has an effect in regular 3D scenes on my system (as with the title screen in my reproduction steps).

[Anth]

24 minutes ago, krbvax said:

Thanks for the prompt check.

I do recall that KSP1 (in that case, the native Linux version) had the same problem with R&D as well as similar 2D menu scenes (mission control, astronaut complex etc). Perhaps there was some Linux-incompatible v-sync method used in the code for those scenes which got carried over into KSP2? V-sync definitely has an effect in regular 3D scenes on my system (as with the title screen in my reproduction steps).

I wonder is that issue would also happen to other Unity games being run in Linux vs Windows.

I am actually on holiday. When I saw this one, it was an easy one to test.
Your other ones are still in the waiting room waiting evaluation.
The Bug Hunters @The Space Peacock and @Spicat when they have time will take a look at them and after being processed/evaluated will send them to the public area.