Page MenuHome

fbx export bug
Closed, DuplicatePublic

Description

System Information
Operating system: Windows-10-10.0.14393-SP0 64 Bits
Graphics card: AMD Radeon(TM) RX Vega 11 Graphics ATI Technologies Inc. 4.5.13571 Core Profile Context 19.30.28 26.20.13028.13

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `rB0330d1af29c0#
Worked: #newest version of Blender that worked as expected#

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file #as simple as possible#]

hi
I try export fbx file but blender get error


I make file in blender 2.83 and edit in blender 2.90

Event Timeline

gobb_blend added a subscriber: gobb_blend.EditedWed, Sep 9, 10:59 AM

I'm having the same issue when exporting certain meshes as FBX. I'm on Blender 2.9. Windows10. Though the issue is also present on 2.83.
I made a minimal test file. A single triangle can cause this error.
To reproduce, simply try to export this as an FBX to any location.

One odd thing that I noticed as an end user is that some of the vertices in the mesh don't appear in the UV Editor. Simply unwrapping the mesh again solves the problem, and export then works as expected. But obviously, this shouldn't even happen in the first place.

@gobb_blend Could you describe how you've created the model that fails to export?

gobb_blend added a comment.EditedWed, Sep 9, 2:11 PM

@Robert Guetzkow (rjg) This issue happened to a coworker of mine, but I'll try to rephrase what they said.
The only noteworthy thing about the creation of this mesh is that they copy-pasted (Ctrl-C, Ctrl-V) the object from one Blender instance to another (both 2.83) and then continued working on the copy. They extruded part of the mesh, and a few of those resulting vertices ended up being broken. The extrusion created new vertices in the mesh, but not in the UV layer -- at least some connections are missing from what I can tell.
Here's a more complete version of the original model with the extruded part clearly emphasized.

What makes this bug even worse is the fact that this broken state is propagated to all vertices created from the broken ones, for example by extruding or loop-cutting them. None of the new vertices will show up in the UV editor.

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Mon, Sep 14, 5:42 PM

@gobb_blend Do you have original file from which this object has been copied? We will need to reproduce this data corruption to fix the problem

gobb_blend added a comment.EditedTue, Sep 15, 10:08 AM


@Richard Antalik (ISS) Here's the original file. Allegedly, pasting this into a new file and then extruding parts of the door frame was enough to cause the issue at hand. Though, even after a handful of tries I haven't been able to reproduce it, so it might be something else entirely.

Thx for the additional information.
This has been reported before, see T79775: Error when exporting FBX (presumably caused by conflicting cached uv customdatalayer) and other merged reports for more information.
Will merge these reports (and also put new information from this one there).