OpenDroneMap / OpenDroneMap/ODM
Bug in the ODM export pipeline for GLTF/GLB
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
GLTF/GLB exporter fails when --texturing-single-material is enabled
Internally, the gltf export step relies on a proper textured mesh, and when single-material is active, the way materials are combined break compatibility with the GLTF export step.
As a result, the GLTF generation step silently fails or is skipped — you get no .glb file.
Contributor 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.
Research direction
Reproduce the ODM export with --texturing-single-material enabled and inspect the GLTF/GLB export pipeline. Confirm the material-combination path remains compatible with GLTF export and that the run produces a .glb file; linked pull request #1906 is already addressing this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100