libretro / libretro/RetroArch

Incorrect estimated screen refresh rate when using the vulkan driver

Open
#18,079 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

I have a monitor with a 60 Hz refresh rate and when I am using the vulkan driver, the estimated screen refresh rate in the settings menu is reporting 120 Hz:

Image

When the video driver is set to d3d11, the estimated screen refresh rate 60 Hz:

Image

I'm not sure if it's related, but when using vulkan and when I have the show fps toggle on, it shows 120 fps in the menu. When I start a core, the fps goes down to 60 fps during game play; however, the motion is not smooth even though the fps remains stable at 60 fps. I need to set the vsync swap interval to 2 in order to get the same level of smoothness that I do when using d3d11 with a swap interval of 1.

Expected behavior

The estimated screen refresh rate setting and the vsync swap interval should match when using d3d11 and vulkan.

Steps to reproduce the bug
  1. Set video driver to vulkan.
  2. Go to the output submenu in the video menu and the estimated screen refresh rate will be double the display-reported refresh rate.
Version/Commit

1.21.0 (05f94af)

Bisect Results

I don't know if this worked in a previous version.

Present in the nightly version

I don't know

Platform & operating system

Windows 11 Pro 24H2 26100.4351

Affected Cores

N/A

Environment information

Video driver: vulkan
GPU: NVIDIA RTX A500 Laptop GPU
Driver: NVIDIA RTX Driver Release 570 version 573.42

Relevant log output
https://gist.github.com/raziel711/9128809357e9cc0bebc514e05f652df0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. First reproduce the issue with the Vulkan driver on the reported Windows setup, compare it with d3d11, and review the linked log; done means the estimated refresh rate, FPS display, and swap-interval behavior no longer differ unexpectedly between the drivers.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, frontend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.