Fix disparity of FBX custom properties import and export #104702
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104702
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Mysteryem/blender-addons:fbx_custom_prop_parity_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?
Light, camera, bone and pose bone properties are now imported to match
the exporter behaviour.
Image custom properties are now exported to match the importer
behaviour, except for Image custom properties that are rarely imported
from a Texture Node instead of a Video Node, which are always exported
to a Video Node.
This resolves one of the issues in #104677.
Fix disparity of FBX custom properties import and exportto Fix disparity of FBX custom properties import and exportThis could help stop so much custom jumping through hoops, custom addons to export to .json and lost data for artists not realizing this is a problem. Thank you for working on this patch.
Having a second patch to support animation would be good.
Here is an older addon that was to get around the lack of it in the exporter
https://mosthostla.com/gamedev/ue4curves/
this imports the animation and exports it on at least armature level custom properties
Seconded - I imagine it'd be a bit more work than the much appreciated import-export-parity patch, but it'd also make those now-better-supported properties substantially more useful (there's a LOT more you can do with animated properties than just static ones).