-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exported OBJ can have invalid face format #391
Comments
Hi @timhutton thanks for report that. As far as I know, the exporter tries to be in accordance with the OBJ specification once it states that (in the file you referenced - as well as me in that forum's thread):
And - because others 3D Apps can read it without any problem - I can not think it would be wrong in that approach. (I could open it in these: ZBrush, Blender, MeshLab, InstantMesh, MS Paint 3D, 3D Converter, Assimp Viewer). So, I tend to think that these small portion of apps that don't process those "// " as face without texture and normal information may have a different understanding of the specification. Something that I suggest in that thread can help the users in these cases:
I just tried it with ParaView and the object was successfully loaded. |
I would not classify this a bug in wings, IMHO that syntax should be valid. Also wings3d have exported OBJ files in this format since 2000 and we have only have had two importers that could not handle trailing '//'. So I would classify this as a bug in the importer lib. |
So I discussed this with Björn and trough the years there have only been complaint on two |
This file was produced by Wings3D: knotty01.zip
Opening it in ParaView gives this error:
The offending line is:
(the first 'f' face line)
It seems that this should be:
since this is a face without texture coordinates or normals. See:
The same thing seems to have caused issues with other software previously: http://www.wings3d.com/forum/showthread.php?tid=865
Thoughts?
Context: I'm not a Wings3D users but have had this issue reported as a downstream user of VTK, which ParaView also uses.
The text was updated successfully, but these errors were encountered: