Vertical frequency core override partly applied when created manually
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Hi !
I have noticed, when creating manually a PUAE.cfg core override to force a 50 Hz vertical frequency, that it was PARTLY applied.
- it did trigger a resolution change of my monitor to 50 Hz
- BUT a "current" frequency of "0.0" Hz was being displayed in the video settings of RA ! Yielding to tearing as it seems that sync to VBL was disabled.
I noticed that, when creating afterwards a core override in the RA settings, things went back to normal (and I did get a popup indicating the core override was indeed loaded).
The question is, I guess, why did it trigger a vertical freq. changed in the first place ?
Thanks a lot :)
Cheers
Configuration : Linux, Ubuntu LTS based (KDE Neon), latest SNAP packaged -- the Flatpak version doesn't manage to set the screen frequency at all)
Contributor 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.
Research direction
Start by reproducing the manually created PUAE.cfg core override on the reported Linux setup, then trace how the override affects display frequency and VBL synchronization. Compare that path with an override created through RetroArch settings; done means both paths report the actual 50 Hz frequency and preserve VBL synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- frontend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100