FBX export error because of invalid NaN UV values. #102783
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#102783
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits
Graphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143
Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash:
b292cfe5a9
Worked: never
Short description of error
Export of an element from attached file in FBX format cause error until UV is not removed.
Tested on 3.2, 3.3.1, 2.79
3.2 fbx error.blend
Added subscriber: @1D_Inc
blender/blender-addons#103583 was marked as duplicate of this issue
#103476 was marked as duplicate of this issue
Screenshot of an error
Added subscriber: @scurest
Cf #79775
Added subscribers: @lichtwerk, @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
@lichtwerk , looks like issue #79775 is not resolved yet
Added subscriber: @96artem1
Removed subscriber: @scurest
Added subscribers: @JJC, @mod_moder
Added subscriber: @Mysteryem-2
Added subscriber: @mont29
Changed status from 'Confirmed' to: 'Needs User Info'
For the records, this is NOT an issue in the FBX code, but in Blender, as stated in #79775, there should be no NaN values in mesh data, this is no valid data.
Would also be good to have info about how that .blend file was generated, we cannot handle data corruption cases just by getting the end result usually, we need steps to reproduce such data corruption.
FBX export error because of UVto FBX export error because of invalid NaN UV values.Such cases are extremely rare, it is hard to find the exact actions sequence. So, this is because of invalid mesh data.
Is it possible to detect such data with a special function?
Thank you for your reply~ I couldn't solve the problem, so I recreated it and worked on it. ~^^;;
@1D_Inc Mesh.validate() should catch and fix these now, at least in master (not sure when UVMaps where moved to the new generic attribute system, old UVMaps did not check for invalid number values, new float attributes do).
Sorry, but what is 'invalid NaN UV values'~?
'NaN' is a short for 'Not a Number', a computer way to represent invalid/'impossible' numbers, like e.g. the result of a division by zero. Such values should never exist in Blender mesh data.
When I tried to merge 10 pieces and export them, I got an error. Is it possible that this problem may occur in the process of merging mash~? Or can it be caused by not doing UV unwrap~?
I thought issue is in FBX code. So the mesh itself is corrupted.
Mesh.validate()
indeed fixes the problem. @1D_Inc , can you verify too?Perhaps we can close the report if above information is not available.
Thanks for the reply.^^ I wanted to know what was causing the problem and solve it, but now I can't. Because It seems that I deleted the blender file ( having problems) while cleaning up the folder~;; If I have the same problem again, I'll contact you again. Thank you~!
@1D_Inc hi, any updates on this?
@PratikPB2123 hi. It is hard to say.
Can fbx export verify meshes before actual export to achieve the solution that doesnot require programming skills at the user side?
For example, different software has "Audit" function which allow to checks and validate the scenes content in cases when such kind of error occurs.
I'm not sure if this is possible.
In some cases, spreadsheet can help to identify the problem
Will close this report for now since the culprit is corrupted mesh and not the FBX export code.
maybe we can track this in a separate report when you find necessary info.