fbx export bug #80584

Closed
opened 2020-09-08 06:53:27 +02:00 by meysam · 13 comments

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: `0330d1af29#
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
error.png
I make file in blender 2.83 and edit in blender 2.90

**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: `0330d1af29# 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 ![error.png](https://archive.blender.org/developer/F8853030/error.png) I make file in blender 2.83 and edit in blender 2.90
Author

Added subscriber: @meysamFk97

Added subscriber: @meysamFk97

Added subscriber: @gobb_blend

Added subscriber: @gobb_blend

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.

cant_export_fbx.blend

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.

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. [cant_export_fbx.blend](https://archive.blender.org/developer/F8857259/cant_export_fbx.blend) 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.

Added subscriber: @rjg

Added subscriber: @rjg

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

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

@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.
cant_export_fbx.blend

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.

@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. [cant_export_fbx.blend](https://archive.blender.org/developer/F8857820/cant_export_fbx.blend) 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.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

@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 Do you have original file from which this object has been copied? We will need to reproduce this data corruption to fix the problem

building1.blend
@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.

[building1.blend](https://archive.blender.org/developer/F8882022/building1.blend) @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.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Thx for the additional information.
This has been reported before, see #79775 (Something in Blender can generate invalid (Nan) values in UVMaps) and other merged reports for more information.
Will merge these reports (and also put new information from this one there).

Thx for the additional information. This has been reported before, see #79775 (Something in Blender can generate invalid (Nan) values in UVMaps) and other merged reports for more information. Will merge these reports (and also put new information from this one there).
Member

Closed as duplicate of #79775

Closed as duplicate of #79775
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#80584
No description provided.