FBX Export: Fix export of meshes with polygons in different order to loops #104498
No reviewers
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104498
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Mysteryem/blender-addons:fbx_fix_unsorted_loop_start_pr"
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?
It was being incorrectly assumed that polygons should always be in the same order as loops.
Exporting such a mesh would raise an error during the export or rarely export geometry layers assigned to the wrong polygons.
Polygons and per-polygon data are now sorted into the same order as loops.
In most cases, polygons will already be in the same order as loops, so this will only add about 0.6ms per 1M polygons exported to the export duration due to a single order check per mesh. With many smaller individual meshes this increases, due to overhead per mesh, up to about 6ms per 1M polygons when each mesh has only 1000 polygons.
In the case where the polygons of a mesh need to be sorted, the main cost is an upfront sorting cost:
For polygons almost already in order, this is about 0.05ms to 0.6ms to 35ms for 100_000, 1M and 10M polygons respectively.
For polygons in random order, this is about 6ms to 85ms to 1300ms for 100_000, 1M and 10M polygons respectively.
There is an additional cost per per-polygon data array to be sorted in the same way, which is about 1ms per 1M polygons per number of arrays to be sorted. There is currently a maximum of two such arrays to be sorted per mesh.