microsoft / microsoft/TRELLIS

Mesh rendering results are worse than 3D gaussians

Open
#151 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13.7k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Description

Hi, Thanks for your brilliant work. I've noticed that your output mesh looked worse that 3DGS results, so the mesh decoder may limit the performance of your generative model. Especially in high frequency parts. I naively blame this to the differentiable rendering of the flexi-cube. Let me know if you have any suggestions on enhancing the rendering quality of output meshes.

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 examining the mesh decoder and the differentiable rendering path involving flexi-cube, then compare its high-frequency results with the 3D Gaussian (3DGS) output. The issue does not identify files, tests, or a concrete acceptance criterion, so the intended quality improvement needs clarification before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-graphics, machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.