Consider separating pixel resolution from framebuffer resolution
Open
- Dominant language
- Rust
- Stars
- 32
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This might be useful if people want to write post-processing anti-aliasing filters, or have an effect produce an output that is higher resolution than the input pixel texture.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating where pixel and framebuffer dimensions are represented and used in the rendering path, then define how separate input and output resolutions should behave and verify the result with a focused example or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100