Automatic refresh rate switching to PAL does not work when starting from command line
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing command-line game loading with the -L core option and compare it with loading the same game after RetroArch has started; the report identifies PUAE, GLCore, and Vulkan as affected. Find where the 50 Hz refresh rate switch is triggered and check why that path is missed during startup. Done means launching with the reported command switches the display to 50 Hz.
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
If I start retroarch and then load game_50Hz.lha, my display switches from 60hz to 50hz.
but if I do:
> retroarch -L /koko/.config/retroarch/cores/puae_libretro.so game_50Hz.lha
Then display is not switched to 50hz.
Expected behavior
Display to switch to 50Hz when starting from command line
Steps to reproduce the bug
> retroarch -L /koko/.config/retroarch/cores/puae_libretro.so game_50Hz.lha
Version/Commit
1.22.2.r10265.34e276c35c-1
Bisect Results
No response
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Archlinux, Retroarch compiled from git source.
Affected Cores
Puae is what I tested.
Environment information
Window Manager: Kwin_wayland
Affected video drivers: GLCore, Vulkan
Compiled and installed from git repo.
Relevant log output
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Event areasOpenlayer:flagship m5 slice topic:World & Travel
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Life-Framework/Life-Framework#2243 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100