Frame throttle seems to be doing nil
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
Perhaps im misunderstanding the functionality of frame throttle? I presumed it was supposed to function as a frame limiter without vsync for the menu? So with vsync off, or a high refresh rate monitor it doesnt run at 100's of fps. On or off, my menu caps at 60. as evidenced by the built in fps monitor.
I've tried in full screen. full screen windowed. windowed. with vsync in retroarch on and off. they all result in the same 60fps cap in the menu.
Expected behavior
I would think it takes off the limiter on fps in the menu.
Actual behavior
I see no difference with it on or off.
Steps to reproduce the bug
- ensure you have fps notifications on
- disable the frame throttle > throttle menu framerate setting
- restart retroarch (no idea if this is necessary or not)
- framerate is unchanged in menu
Bisect Results
[Try to bisect and tell us when this started happening]
Version/Commit
You can find this information under Information/System Information
- RetroArch: 1.87 54fd445c75
Environment information
- OS: Win10
- Compiler: [In case you are running local builds]
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 behavior in RetroArch 1.87 on Windows 10 with FPS notifications enabled, comparing the menu with the throttle menu framerate setting on and off. Done means determining whether the setting is expected to change the observed menu framerate and documenting the result or a confirmed fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100