Stays on Menu when running/resuming core - going back and forth several times cures it
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
With any core, when starting or resuming a game ('Run' or 'Resume' from the menu), sometimes the menu will stay on-screen and the game will start in the background (can hear it running). The menu is non-responsive, and only using the hotkey to go back to the menu will make it accessible again. Sometimes have to do this several times (i.e. hotkey to menu, then Resume) to eventually get in-game, or sometimes it just goes straight in.
Expected behavior
Game starts or resumes when selecting the option from the menu
Actual behavior
Game starts/resumes, but display not being updated. Have to flick between menu and start resume (sometimes once, sometimes several times) in order to get in-game. Doesn't seem to matter which Core.
Steps to reproduce the bug
- Start Retroarch
- Load a game (either long way via Load Core, Load Content etc or just by going to History and selecting a game from there)
- Start game
Version/Commit
This happens when I build from the current Repo i.e. post v1.13.0
- RetroArch: [version/commit]
Environment information
Linux, MIYOO/RS90 version (RGUI menu), sdl_rs90 graphics driver
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 Linux using the MIYOO/RS90 build, the RGUI menu, and the sdl_rs90 graphics driver. Start at the Run and Resume menu actions and observe when the game begins while the menu remains visible. Done means selecting either action consistently leaves the menu and displays the running game.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100