FBX import fails with long custom property names #53812
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#53812
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
{F1864160}System Information
Mac OS 10.12.6
NVIDIA GeForce GT 750M
Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)
Short description of error
When importing an FBX I get the traceback listed below. I don't understand where the key length limit comes from, but there appears to be a long custom property name that exceeds this limit. If I add the below lines to
import_fbx.py
L318, the FBX imports correctly.Exact steps for others to reproduce the error
Added subscriber: @FreakTheMighty
Added subscribers: @mont29, @lichtwerk
Can confirm the limitation, but it is a known limitation.
The limit was raised from 32 a couple of years back.
Now capping the prop name at 63 chars might work in some cases but ask for more trouble [in case of multiple colliding very long names].
Not sure what the best strategy is here: have some very generic way of handling such very long idprops? Leave to the exporting app/user to respect this limitation?
Confirming for now (as it throws an error), but would kindly ask @mont29 for an opinion...
If we're worried about collisions, maybe we could replace the ID with some sort of UUID or content hash when it exceeds the limit. I'm not really sure what the side effects of changing the ID are, but the import seemed to work fine as far as my needs go.
This issue was referenced by
3dc0ceb198
Changed status from 'Open' to: 'Resolved'