Ralith / Ralith/hypermine

Indexed chunk rendering

Open
#109 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue performance
Dominant language
Rust
Stars
202
Forks
22
Avg merge
6h 8m
Merged PRs (30d)
7

Description

We could potentially reduce vertex workload by 1/3 via the post-transform cache by supplying a simple static index buffer for a chunk's worth of faces. The index buffer is the same for all chunks because each chunk is a series of quads.

Best to pursue this after establishing a rendering benchmark, so any actual performance impact can be measured.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by establishing the rendering benchmark requested in the issue, then inspect the existing chunk rendering path and how faces are submitted. Evaluate a shared static index buffer for the quad faces and compare it with the baseline; done means the performance impact is measured and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
computer-graphics, game-dev, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.