libretro / libretro/RetroArch

Wrong estimated screen refresh rate

Open
#19,183 2 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

Here Lubuntu 24.04.3 kernel 6.14.
RetroArch 1.22.2 2c16033 2027-07-01

In setting video output the "estimated screen refresh rate" is showing a wrong value monitor screen Hz.
Here the monitor use 60 Hz.
When "estimated screen refresh rate" reach 2048 sample is showed a value Hz below of 21 for screen Hz.
Have some cores if disabling vertical sync does a speed up above of 300 % speed even not enabling fast forward.
That issue not happen in Retroarch 1.21.
Only reporting.
I have uploaded a log.
Have a nice week.

log.zip

Expected behavior

No response

Steps to reproduce the bug

see above

Version/Commit

1.22.2 2c16033

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Linux Lubuntu 24.04.3

Affected Cores

No response

Environment information

Session X11

Relevant log output

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

Start by reviewing the attached log.zip and the video output settings involved in the estimated screen refresh rate on RetroArch 1.22.2 under Linux Lubuntu 24.04.3 with X11. Compare the reported value and core speed behavior with RetroArch 1.21; done means the 60 Hz monitor is estimated correctly and disabling vertical sync does not cause the reported speed increase.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.