Not possible to export "Empty Hair" curve as FBX #105260
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#105260
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: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86
Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: (newest version of Blender that worked as expected)
Short description of error
[Not possible to export "empty hair" geo node setup, it consist of the curves being extruded on x to make a plane and mapping the "hair card" on it]
Exact steps for others to reproduce the error
Test File
Was originally reported by @kristians.dzenis on blender/blender#120102 , thought this should still be fixed. I think the main problem with this is that these exporters doesn't support
CURVES
object type yet, and I tried to add it back, butnew_from_object
doesn't like that either. So might worth taking a look further.The reported issue doesn't seem to be related to instances or
Realize Instances
at all, but rather is a general issue with exporting anyCURVES
objects which have been converted to mesh data, e.g. throughCurve to Mesh
.This seems like it could be a bug that
bpy.data.meshes.new_from_object()
is unable to find the mesh data of the evaluatedCURVES
object, becausenew_from_object
usually ends up with the same result asbpy.ops.object.convert(target='MESH')
(Object
>Convert
>Mesh
) when usingpreserve_all_data_layers=True
anddepsgraph=bpy.context.evaluated_depsgraph_get()
.bpy.ops.object.convert(target='MESH')
is able to find and convert the mesh data to a new Mesh object, butnew_from_object
is not.I did find that the mesh data of
CURVES
objects can be accessed through the depsgraph's instances (bpy.context.evaluated_depsgraph_get().object_instances
), which can similarly be used to access the mesh data of a legacyCURVE
object which has a Bevel, but I don't think this should be the necessary way to get the mesh data of evaluatedCURVES
objects when other Object types work withnew_from_object
.The attached Blend has a simplified version of the .blend in the original report and has a script that does the conversion to mesh through the depsgraph's instances, and compares it to
bpy.ops.object.convert(target='MESH')
.