Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Viewport appearance: normal shading, transparency, textures and color management

Open
  • Is something wrong?
#49 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
computer-graphics

Research direction

Start with known-issues.md and the README Architecture section, which list the unsupported appearance features (materials, transparency, normal shading, textures, color management). Each stage needs a comparison against the pinned Maya reference in issue #5 before it can be claimed, and the MCP docs in .project-docs/mcp.md must be updated in the same change. Scope spans rendering, MCP and native checks, so pick one stage and confirm it with maintainers first.

Written by the indexing model from the issue text.

Description

area/rendering area/viewport type/feature

Problem

The GPU preview is opaque, depth-tested and unshaded; appearance is reported as incomplete.

Current behavior

known-issues.md; README Architecture: materials, transparency, normal shading, textures and document color management unsupported. Corner normals and texture lookup are not rendered.

Expected behavior

Staged viewport appearance with explicit unsupported diagnostics preserved until each stage lands.

Acceptance criteria

  • Comparison against the pinned reference per stage; no color processor claim without evidence.
  • Unimplemented controls stay visibly disabled with a reason; no dummy tools or controls.
  • MCP coverage in the same change: implemented operations and relevant state exposed with synchronized tool schemas, real Editor protocol tests (scene token, draft, modal, close and busy guards) and updates to .project-docs/mcp.md and its coverage inventory.
  • Native visual check of the real window (screenshot reviewed), not only headless tests.
  • Tests cover malformed, empty, boundary and failure cases; failed operations preserve the baseline.
  • No parity claim without comparison against the pinned Maya reference (#5); unverified constants are documented as provisional.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.