Viewport grid is drawn through opaque meshes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 34/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- computer-graphics, desktop-dev
Research direction
The bug is in the viewport grid pass, which is not named by file. Start from known-issues.md line 14, then find where the grid is drawn and check its depth state and its order relative to the mesh pass. Reproducing needs macOS with Metal and the MCP stdio server, using a cube and orbit_camera. Done means grid lines stay hidden behind front faces of opaque meshes, checked against the Maya 2026 viewport behaviour the issue cites.
Written by the indexing model from the issue text.
Description
On macOS (Metal, debug build of main plus the cylinder/cone branch), the viewport grid at y=0 is drawn across the front faces of opaque meshes. Every grid line passing behind a mesh appears on its front faces.
Repro, through the MCP stdio server:
create_primitivecube, cylinder or cone. Each is centred at the origin, so the y=0 grid plane cuts through it.frame_selected.orbit_camerawith radians[0.5, 0.45], looking down at the object.
The grid lines stay visible across the front side faces. A primitive spanning y = -1..1 shows it clearly. The status overlay says "Opaque geometry preview".
Expected: the depth test hides the grid behind front faces. Maya's grid is depth-occluded by shaded geometry. This needs checking against the Maya 2026 viewport docs before any parity claim is made.
Suspects: the grid pass runs without depth testing, runs after the mesh pass without a depth attachment, or uses a depth comparison that always passes. known-issues.md line 14 says only that Grid composition is "pending", so this is not documented as a known limitation.
The captures are kept locally and are not attached.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 2
- Avg merge
- 2h 28m
- Merged PRs (30d)
- 76
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from cristim/AztecCraft
-
area/viewport type/chore
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#186 ·
Maintainers usually reply within 1 day
-
area/infra type/chore
Difficulty 1/5 Under an hour Newbie friendliness 94/100
cristim/AztecCraft#181 ·
Maintainers usually reply within 1 day
-
area/modeling type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cristim/AztecCraft#176 ·
Maintainers usually reply within 1 day
-
area/modeling type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cristim/AztecCraft#175 ·
Maintainers usually reply within 1 day
-
area/ui-parity type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cristim/AztecCraft#172 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day
-
bug documentation sev-0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1620 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100