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

Aperta
#20,107 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
57/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C
Stelle
14.6k
Fork
2.4k
Merge medio
2g 3h
PR unite (30g)
64

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di libretro/RetroArch

Tutte le issue di libretro/RetroArch

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.