libretro / libretro/RetroArch

Default refresh rate overridden by some core options

Open
#13,181 1 comment 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

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

In the Genesis-Plus-GX core, changing the interlaced mode option causes the refresh to be changed to 59.94Hz.

This results in stuttering if previously configured to run with 60Hz.

Expected behavior

Core to not override frontend settings.

Actual behavior

Core forces refresh rate change with no option to disable enforcement.

Steps to reproduce the bug

Set Refresh Rate to 60Hz

Disable Windowed Fullscreen

Enable Fullscreen

Start a game in the Genesis-Plus-GX core and set Interlaced Mode 2 Output to Double Field

Bisect Results

Commit cfcd0a7a0d06f47c1f5dce8690a6ef6ae1b76034

Version/Commit

Stable 1.9.12 and latest nightly 4b16b4f

All Genesis-Plus-GX core builds over the past few years exhibit the issue.

Environment information

Windows 11

Additional Info:

https://github.com/libretro/RetroArch/blob/4b16b4fe9a08ddaa63d03b0054cff74a7ecddaf1/retroarch.c#L10632

Changing 59.94 to 60.00 prevents issue.

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

Inspect retroarch.c around line 10632 and reproduce the issue with the Genesis-Plus-GX core using the listed fullscreen, refresh-rate, and Interlaced Mode 2 Output settings. Verify that changing the interlaced mode no longer overrides a frontend-configured 60Hz refresh rate, while confirming the existing reproduction no longer stutters.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.