Traceback error while exporting as fbx #96951

Closed
opened 2022-04-01 15:06:41 +02:00 by Carol · 4 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.33

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

Short description of error
Unable to export as fbx

FBX export starting... 'C:\\Users\\Yalin\\Downloads\\新建文件夹 (2)\\gun.fbx'
Python: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\__init__.py", line 644, in execute
    return export_fbx_bin.save(self, context, **keywords)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3213, in save
    ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3109, in save_single
    fbx_objects_elements(root, scene_data)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 2909, in fbx_objects_elements
    fbx_data_mesh_elements(objects, me_obj, scene_data, done_meshes)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1177, in fbx_data_mesh_elements
    elem_data_single_int32_array(lay_uv, b"UVIndex", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\fbx_utils.py", line 505, in elem_data_single_int32_array
    return _elem_data_single(elem, name, value, "add_int32_array")
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\fbx_utils.py", line 452, in _elem_data_single
    getattr(sub_elem, func_name)(value)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\encode_bin.py", line 161, in add_int32_array
    data = array.array(data_types.ARRAY_INT32, data)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1177, in <genexpr>
    elem_data_single_int32_array(lay_uv, b"UVIndex", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx)))
KeyError: ((nan, nan), 0)

location: <unknown location>:-1

Exact steps for others to reproduce the error
I only remembered that I imported an auto-mirror

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.33 **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Worked: (newest version of Blender that worked as expected) **Short description of error** Unable to export as fbx ``` FBX export starting... 'C:\\Users\\Yalin\\Downloads\\新建文件夹 (2)\\gun.fbx' Python: Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\__init__.py", line 644, in execute return export_fbx_bin.save(self, context, **keywords) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3213, in save ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3109, in save_single fbx_objects_elements(root, scene_data) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 2909, in fbx_objects_elements fbx_data_mesh_elements(objects, me_obj, scene_data, done_meshes) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1177, in fbx_data_mesh_elements elem_data_single_int32_array(lay_uv, b"UVIndex", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx))) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\fbx_utils.py", line 505, in elem_data_single_int32_array return _elem_data_single(elem, name, value, "add_int32_array") File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\fbx_utils.py", line 452, in _elem_data_single getattr(sub_elem, func_name)(value) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\encode_bin.py", line 161, in add_int32_array data = array.array(data_types.ARRAY_INT32, data) File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1177, in <genexpr> elem_data_single_int32_array(lay_uv, b"UVIndex", (uv2idx[uv_id] for uv_id in _uvtuples_gen(t_luv, t_lvidx))) KeyError: ((nan, nan), 0) location: <unknown location>:-1 ``` **Exact steps for others to reproduce the error** I only remembered that I imported an auto-mirror
Author

Added subscriber: @HakunaMytata

Added subscriber: @HakunaMytata

Added subscriber: @mano-wii

Added subscriber: @mano-wii

The object has corrupted UVs.
Did this object come from some old file?
This was a common problem some time ago as some operator in Blender was corrupting the UVs.

You can run this code in the Blender console or in the text editor to "fix" the mesh.

import bpy
for me in bpy.data.meshes:
     me.validate()

Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further.

Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.

The object has corrupted UVs. Did this object come from some old file? This was a common problem some time ago as some operator in Blender was corrupting the UVs. You can run this code in the Blender console or in the text editor to "fix" the mesh. ``` import bpy for me in bpy.data.meshes: me.validate() ``` Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further. Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.

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
2 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#96951
No description provided.