[Bug] Menu Frame Throttle doesn't work properly in 1.19.1
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
I'm having insane coil whine on my desktop PC when browsing the RetroArch menu. This happens with glui and xmb (haven't tried the others). When I go to Frame Throttle and enable "Sync to extract content framerate" and "throttle menu framerate" it works until I quit RetroArch and start it again (even after manually saving the config). After the restart I have to switch the menu driver and disable en re-enable the menu framerate throttle but it doesn't stay that way when I relaunch the app.
I'm running Retroarch 1.19.1 Git Version: 427e2fa6f6 under Windows 11.
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
Reproduce the issue on Windows 11 with RetroArch 1.19.1, using the glui or xmb menu and the reported Frame Throttle settings. Inspect how the menu framerate throttle is saved and restored across relaunches; done means the setting remains effective after restarting without switching the menu driver.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100