casey / casey/pxl

Consider separating pixel resolution from framebuffer resolution

Open
#108 0 comments 0 reactions 0 assignees View on GitHub
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

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.