- Addon: Send to Unreal
- Steps to Reproduce the Problem: In a Blender file with a Skeletal Mesh (armature) that has multiple actions, I clicked Pipeline > Export > Settings Dialogue, then set it to "Send to Disk" instead of Unreal, then adjusted to uncheck
Export custom property fcurves under Export -> Animation, then "Push Assets"
- Error Log:
Python: Traceback (most recent call last):
File "C:\Users\capti\AppData\Roaming\Blender Foundation\Blender\5.0\scripts\addons\send2ue\operators.py", line 73, in modal
raise error
File "C:\Users\capti\AppData\Roaming\Blender Foundation\Blender\5.0\scripts\addons\send2ue\operators.py", line 63, in modal
function(*args, **kwargs)
File "C:\Users\capti\AppData\Roaming\Blender Foundation\Blender\5.0\scripts\addons\send2ue\core\export.py", line 281, in export_animation
export_custom_property_fcurves(action_name, properties)
File "C:\Users\capti\AppData\Roaming\Blender Foundation\Blender\5.0\scripts\addons\send2ue\core\export.py", line 135, in export_custom_property_fcurves
fcurve_data = utilities.get_custom_property_fcurve_data(action_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\capti\AppData\Roaming\Blender Foundation\Blender\5.0\scripts\addons\send2ue\core\utilities.py", line 218, in get_custom_property_fcurve_data
for fcurve in action.fcurves:
^^^^^^^^^^^^^^
AttributeError: 'Action' object has no attribute 'fcurves'
- OS: Windows 11
- Addon Version: i.e. Send to Unreal 2.6.7
- Blender Version: i.e. Blender 5.0.0
- Unreal Version: N/A
I managed to work around this by removing functions/references to fcurves in my local export.py file, but if someone does need to export custom property fcurves and/or doesn't want to modify the addon this'll block exporting animated meshes. I do not get this error on a file with no animations.
For added context, this did not used to happen on Blender 4.x.x + Send to Unreal 2.6.5, I'm not sure which end upgrading broke it.
Export custom property fcurvesunder Export -> Animation, then "Push Assets"I managed to work around this by removing functions/references to fcurves in my local
export.pyfile, but if someone does need to export custom property fcurves and/or doesn't want to modify the addon this'll block exporting animated meshes. I do not get this error on a file with no animations.For added context, this did not used to happen on Blender 4.x.x + Send to Unreal 2.6.5, I'm not sure which end upgrading broke it.