CRT filters can't be used because of forced "high res output"
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 35
- Forks
- 48
- Avg merge
- 10h 45m
- Merged PRs (30d)
- 7
Description
The latest Hatari core won't work properly with CRT filters since a real 320x200 (or 320x200 plus borders) screen is not passed to Retroarch.
The screen is alway in higher resolution in order to being able to show Hatari's internal menu, but that makes CRT expecting low res framebuffers work improperly.
Contributor guide
No contributing guide indexed for this repository
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 issue with the Hatari core and a RetroArch CRT filter, comparing the current high-resolution output with the expected 320x200 or bordered framebuffer. Trace where the core selects its output resolution and determine what behavior is required for both the internal menu and CRT-filter-compatible frames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100