Blur Busters Forums

PacketAuditor wrote: ↑

27 Jul 2023, 09:11

Is V-Sync from the compositor equivalent to enabling V-Sync in NVCP on Windows?

jorimt wrote: ↑

27 Jul 2023, 09:47

PacketAuditor wrote: ↑

27 Jul 2023, 09:11

Is V-Sync from the compositor equivalent to enabling V-Sync in NVCP on Windows?

G-SYNC only uses V-SYNC's VBLANK signal adherence to ensure the tearline is steered offscreen at all times when the framerate is within the refresh rate, regardless of what double buffer method you use, so if Wayland's method is functioning and is of the double buffer variety, it should be fine for use with G-SYNC.

PacketAuditor wrote: ↑

27 Jul 2023, 11:18

So if the Wayland compositor (KWin) is using triple buffering it will not provide good latency results?

PacketAuditor wrote: ↑

27 Jul 2023, 11:18

Sorry, I am just starting out with Linux and just want to have an equivalant VRR experience to Windows.

jorimt wrote: ↑

27 Jul 2023, 11:24

Triple buffer will still work to prevent tearing, but could potentially add extra latency/issues due to its extra buffer (G-SYNC operation is natively double buffer).


I have zero Linux experience, so can't help you there.

PacketAuditor wrote: ↑

27 Jul 2023, 09:11

I use G-Sync + V-Sync + frame cap normally on Windows.

Is V-Sync being forced on Wayland really a problem then? Is V-Sync from the compositor equivalent to enabling V-Sync in NVCP on Windows?

I am trying to figure out if with the upcoming 545 Nvidia driver (when multi-monitor G-Sync will be fixed on Wayland) if it will be equivalant to a Windows experience.

Thanks!

Kyouki wrote: ↑

27 Jul 2023, 11:47

I recently became a massive Linux nerd and on my quest to figure things out on that platform, I have found several resources that say kwin/kde plasma in general has the option now to disable and allow tearing to occur (thus no vsync) though, there is more to the story found here:
https://zamundaaa.github.io/wayland/202 ... yland.html

As proven here:
https://invent.kde.org/plasma/kwin/-/merge_requests/927

and I can see this option within my Arch build with KDE Plasma/kwin.
So no, not anymore. I mostly played on a laptop from work to mess around with things within the OS and found it barely to affect me as a latency sensitive person in general.

PacketAuditor wrote: ↑

27 Jul 2023, 11:52

Kyouki wrote: ↑

27 Jul 2023, 11:47

I recently became a massive Linux nerd and on my quest to figure things out on that platform, I have found several resources that say kwin/kde plasma in general has the option now to disable and allow tearing to occur (thus no vsync) though, there is more to the story found here:
https://zamundaaa.github.io/wayland/202 ... yland.html

As proven here:
https://invent.kde.org/plasma/kwin/-/merge_requests/927

and I can see this option within my Arch build with KDE Plasma/kwin.
So no, not anymore. I mostly played on a laptop from work to mess around with things within the OS and found it barely to affect me as a latency sensitive person in general.

I do want V-Sync so that I can use G-Sync "as intended" and according to the blurbusters guide (G-Sync + V-Sync + frame cap).

Do you know if the KWin V-Sync + G-Sync will function the same as NVCP V-Sync + G-Sync in Windows? And if not, can I just disable V-Sync in the compositor like you said is now possible, and then enable V-Sync in NVCP on Linux to achieve the optimal configuration?

THANKS! <3