microsoft / microsoft/TRELLIS.2
mesh2ovoxel and ovoxel2mesh test
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.3k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
I test these scripts:https://github.com/microsoft/TRELLIS.2/tree/main/o-voxel/examples.
(1) rec_mesh is much bigger than scale mesh.
(2) if export to glb, loss hanppened!
Is it right?
EDIT: seems caused by this, too slow! if skip to the simplify! Maybe the simplify has some bugs!
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the mesh2ovoxel and ovoxel2mesh examples in o-voxel/examples and compare rec_mesh with the scaled mesh and GLB export. Inspect o-voxel/o_voxel/postprocess.py around line 185, then compare behavior with the linked CuMesh simplify issue. Done means determining whether simplification causes the size or export loss and documenting a reproducible result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100