FPS counter OSD still shows 60 FPS on 30 FPS games when Skip Duplicate Frames is enabled.

Open
#20,107 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
frontend

Research direction

Trace the duplicate-frame skip path and the built-in Display Frame Rate counter in RetroArch’s video and on-screen display code. Start by searching for the Skip Duplicate Frames setting and the counter’s frame accounting, then compare how submitted and actually presented frames are counted. Done means the counter reports about 30 FPS in the described 30 FPS game at 60 Hz, while normal frame-rate reporting remains correct.

Written by the indexing model from the issue text.

Description

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

When Settings > Video > Synchronization > Skip Duplicate Frames is turned on and a core sends duplicate-frame signals for a 30 FPS game running in a 60 Hz video mode, RetroArch stops presenting the duplicate frames as expected. External frame-rate overlays and frame-generation tools (such as MSI Afterburner and Lossless Scaling) correctly show 30 FPS.

However, RetroArch's built-in FPS counter (Settings > On-Screen Display > On-Screen Notifications > Display Frame Rate) continues to show ~60.00 FPS instead of ~30.00 FPS.

Expected behavior

When Skip Duplicate Frames is enabled and RetroArch skips presenting duplicate frames, RetroArch's built-in FPS counter should show the actual displayed frame rate (~30.00 FPS), matching what external overlays report.

Steps to reproduce the bug
  1. Enable Settings > Video > Synchronization > Skip Duplicate Frames.
  2. Enable Settings > On-Screen Display > On-Screen Notifications > Display Frame Rate.
  3. Launch a 30 FPS game in a 60 Hz mode using a core that supports duplicate-frame detection (for example, beetle-psx-libretro with Frame Duping enabled).
  4. Compare RetroArch's built-in FPS counter with an external overlay such as MSI Afterburner: external tools show 30 FPS, while RetroArch's FPS counter still shows 60.00 FPS.
Version/Commit

1.22.2 (Git bfb8c15)

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Windows 11

Affected Cores

Any core that signals duplicate frames when Skip Duplicate Frames is enabled (tested with beetle-psx-libretro)

Environment information
  • Video driver: Vulkan
Relevant log output

Dominant language
C
Stars
14.6k
Forks
2.4k
Avg merge
2d 5h
Merged PRs (30d)
63

Getting set up

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.

More from libretro/RetroArch

All issues in libretro/RetroArch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.