Problem importing OBJ files (probably assimp problem, not assimpNet)
- Dominant language
- C#
- Stars
- 218
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
I have some OBJ which imported correctly in 3.3.1 and doesn't work on 4. doesntWork.obj does not expose the texture correctly, while works.OBJ does.
The only difference is where the g (group) and usemtl are placed. Tinkering with the OBJ file, I think that the "group" must be defined after the "mtllib". If not, the problem happens.
I don't know if this is a malformed OBJ file either. The OBJ format is ... well... very badly defined. Both OBJ files correctly load on 3DSMax 2013 though.
objs (renamed)
[doesntWork.txt](https://github.com/assimp/assimp-net/files/2525206/doesntWork.txt)
[works.txt](https://github.com/assimp/assimp-net/files/2525207/works.txt)
material (renamed... but any material and texture file will do, the problem seems to be in the OBJ)
[floorTest.txt](https://github.com/assimp/assimp-net/files/2525219/floorTest.txt)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by importing the attached doesntWork.txt and works.txt OBJ samples with floorTest.txt and compare their group, mtllib, and usemtl ordering. Read the OBJ import path and verify the reported texture difference; done means the issue is reproduced and either the differing files import consistently or the malformed-file behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100