Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tech question] GPU usage in 60Hz vs 120Hz+VsyncSwapPeriod=2 #558

Open
vanfanel opened this issue Nov 8, 2024 · 2 comments
Open

[Tech question] GPU usage in 60Hz vs 120Hz+VsyncSwapPeriod=2 #558

vanfanel opened this issue Nov 8, 2024 · 2 comments

Comments

@vanfanel
Copy link

vanfanel commented Nov 8, 2024

Hello there,

My iGPU (Intel XE on an i5-1235U) doesn't provide VRR over HDMI (it's 2.0 only), so to prevent input lag caused by VSYNC, I run most LibRetro cores on a 120Hz mode with Vsync Swap Period set to 2.
That's supposed to tax the GPU the same as 60Hz with Vsync Swap Period set to 1, not more, but I am seeing that some games (Conquer, for example) are showing performance problems with 120Hz+Vsync Swap Period set to 2, while they are fullspeed at 60Hz with Vsync Swap Period set to 1.

This is something I am only seeing on this particular core, and only with the ParaLLEI graphics plugin.
Is it a known issue? Is this plugin somehow hammering the GPU at 120Hz even if Vsync Swap Period is set to 2?

Thanks!

@golivax
Copy link

golivax commented Dec 2, 2024

Similar situation here. I can't get a fully stable 60fps on Goldeneye and Cruisn USA on an Rog Ally if I'm running 120Hz + Sync to Exact Content Framerate (Vsync off) with Mupen64plus Next and Parallel plugin. It seems to tax the GPU like crazy for whatever reason.

@vanfanel
Copy link
Author

vanfanel commented Dec 2, 2024

Yes, but it's obviously wrong: 120Hz + Vsync Swap Period = 2 should result in the same number of frames being rendered as 60Hz + Vsync Swap Period = 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants