Screen resolution doesn't apply when in an override
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
screen resolution doesn't apply when in an override
Expected behavior
When changing output res from 1920X1080 to 1366X768, saving override by content directory, quiting RA, entering back with the same core and content directory,, the output res should be saved
Actual behavior
Output res changed but does not apply. When looking at the screen resolution in the RA menu it is still on 1920X1080
Steps to reproduce the bug
1.Changing output res from 1920X1080 to 1366X768
2. Saving override by content directory
3. Quiting RA, entering back with the same core and content directory
4. The output res is still 1920X1080
Bisect Results
[Try to bisect and tell us when this started happening]
Version/Commit
You can find this information under Information/System Information
- RetroArch: [version/commit]
1.14.0
Environment information
- OS: Windows 10
- 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
No source files, tests, or entry points are named. Reproduce this on RetroArch 1.14.0 for Windows 10 using a content-directory override, then trace how the screen resolution setting is saved and reloaded; done means 1366x768 remains selected after quitting and reopening with the same core and content directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100