White horizontal plane artifact in generated GLB File
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision, machine-learning
Research direction
No file, test, or entry point is named. Start by reproducing the single-image reconstruction and tracing whether the plane originates in layout prediction or Gaussian splatting-to-mesh conversion; done means identifying a confirmed cause or documented configuration or fix for the artifact.
Written by the indexing model from the issue text.
Description
Description
When using SAM3D for single-image 3D reconstruction, the generated GLB mesh often includes an unwanted flat horizontal plane at the bottom or top of the object. This plane appears as a white/gray flat surface that is not part of the original object.
Problem Details
The artifact appears as:
- A flat horizontal mesh at the bottom of the reconstructed object (most common)
- Sometimes at the top of the object
- The plane has normals pointing up (Y-axis) or down
- It appears regardless of the input image content
Questions
- Is there a parameter or configuration to prevent this artifact?
- Is this related to the layout prediction or the Gaussian splatting to mesh conversion?
- Are there plans to address this in future releases?
Related Issues
#123 - Generate weird cross objects (similar geometric artifacts)
#128 - Improving geometry and back-view reconstruction
Thanks for the great work on SAM 3D, any guidance on this issue would be appreciated !
- Dominant language
- Python
- Stars
- 7.6k
- Forks
- 897
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 facebookresearch/sam-3d-objects
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
V60Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
facebookresearch/sam-3d-objects#202 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in facebookresearch/sam-3d-objects
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ClockGU/clockwork-backend#169 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#616 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
chnm/teachinghistory-hugo#47 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pandas-dev/pandas-stubs#2047 · 2 comments ·
Maintainers usually reply within 1 day