Page MenuHome

Export Wavefront OBJ incorrect
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 530 Intel 4.5.0 - Build 27.20.100.8682

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: rBc77597cd0e15
Worked: (newest version of Blender that worked as expected)

Addon Information
Name: Wavefront OBJ format (3, 9, 0)
Author: Campbell Barton, Bastien Montagne

Short description of error
When exporting to OBJ some meshes have extra faces where is meant to be void.

Please see attached blender file
The arch is obtained from a cube with a cylinder (boolean)
You can see that the OBJ rendering still has extra faces covering the arch. This is not how it appears in the viewport.

Event Timeline

Domenico (Realgigabyte) renamed this task from Export Wavefront OBJ incorret to Export Wavefront OBJ incorrect.Mar 11 2022, 3:17 PM
Domenico (Realgigabyte) created this task.
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Mar 11 2022, 3:32 PM

I can't see these "extra faces" by importing the attached .obj file.
Could you provide an image showing the problem?

Are you using the new OBJ Exporter or the old python add-on? (The new one is just called Wavefront OBJ, the old one has "Old" in its name)

I can't see these "extra faces" by importing the attached .obj file.
Could you provide an image showing the problem?

I am not in my pc now but can try to open with the Windows 3D Viewer i can see the problem there (and when I try to import to other applications)

This how it looks when opened on other apps:

Hi, I just would like to add that the problem with 3rd party compatibility is resolved if "Triangulated Mesh" option is selected in the export dialog.
Selecting this option all meshes are visualized correctly.

The problem is not in Blender then.
Blender exports as a polygon. The software that has to triangulate it.

I suggest you report the problem in the bug tracker of the app with the issue.

Thanks for the report anyway.