FBX Import: ValueError: not enough values to unpack (expected 2, got 1) casued by UDP3DSMAX custom attribute #76768

Closed
opened 2020-05-14 21:29:15 +02:00 by Felix · 4 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: blender/blender@375c7dc4ca
Worked: I didn't test other versions

Short description of errorBlender2.82a_fbx_import_bug.zip
Exporting geometry from Maya with a custom attribute called UDP3DSMAX with any value to an *.fbx will result to an import error in blender.
" ValueError: not enough values to unpack (expected 2, got 1) "

Traceback (most recent call last):
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\__init__.py", line 217, in execute
    if import_fbx.load(self, context, filepath=path, **keywords) == {'FINISHED'}:
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2813, in load
    _(); del _
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2807, in _
    root_helper.build_hierarchy(fbx_tmpl, settings, scene, view_layer)
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2242, in build_hierarchy
    child.build_hierarchy(fbx_tmpl, settings, scene, view_layer)
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2229, in build_hierarchy
    obj = self.build_node_obj(fbx_tmpl, settings)
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2041, in build_node_obj
    blen_read_custom_properties(self.fbx_elem, obj, settings)
  File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 331, in blen_read_custom_properties
    prop_name, prop_value = item.split('=', 1)
ValueError: not enough values to unpack (expected 2, got 1)

location: <unknown location>:-1

I didn't find any other attribute names that would do the same. This only occurred to me because the source was a *.3dm file.
The error doesn't appear when I empty or delete this attribute (type: string). The error also comes up with a new, created object in Maya, that I add a custom attribute with this name.
I Used Maya 2018 for the test files. I got the same results with Maya 2019/2020.

The *.fbx files slightly differ on bit level, but contain the same geometry (a rectangular plane).

Exact steps for others to reproduce the error
import the example fbx files

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `blender/blender@375c7dc4ca` Worked: I didn't test other versions **Short description of error**[Blender2.82a_fbx_import_bug.zip](https://archive.blender.org/developer/F8536010/Blender2.82a_fbx_import_bug.zip) Exporting geometry from Maya with a custom attribute called UDP3DSMAX with any value to an *.fbx will result to an import error in blender. " ValueError: not enough values to unpack (expected 2, got 1) " ``` Traceback (most recent call last): File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\__init__.py", line 217, in execute if import_fbx.load(self, context, filepath=path, **keywords) == {'FINISHED'}: File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2813, in load _(); del _ File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2807, in _ root_helper.build_hierarchy(fbx_tmpl, settings, scene, view_layer) File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2242, in build_hierarchy child.build_hierarchy(fbx_tmpl, settings, scene, view_layer) File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2229, in build_hierarchy obj = self.build_node_obj(fbx_tmpl, settings) File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 2041, in build_node_obj blen_read_custom_properties(self.fbx_elem, obj, settings) File "D:\Program Files\blender-2.82a-windows64\2.82\scripts\addons\io_scene_fbx\import_fbx.py", line 331, in blen_read_custom_properties prop_name, prop_value = item.split('=', 1) ValueError: not enough values to unpack (expected 2, got 1) location: <unknown location>:-1 ``` I didn't find any other attribute names that would do the same. This only occurred to me because the source was a *.3dm file. The error doesn't appear when I empty or delete this attribute (type: string). The error also comes up with a new, created object in Maya, that I add a custom attribute with this name. I Used Maya 2018 for the test files. I got the same results with Maya 2019/2020. The *.fbx files slightly differ on bit level, but contain the same geometry (a rectangular plane). **Exact steps for others to reproduce the error** import the example fbx files
Author

Added subscriber: @BOBtheROSS

Added subscriber: @BOBtheROSS
Felix changed title from FBX Import: ValueError: not enough values to unpack (expected 2, got 1) to FBX Import: ValueError: not enough values to unpack (expected 2, got 1) casued by UDP3DSMAX custom attribute 2020-05-14 21:39:18 +02:00

Added subscribers: @mont29, @rjg

Added subscribers: @mont29, @rjg

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Robert Guetzkow self-assigned this 2020-11-27 13:47:33 +01:00

Blender 2.90.1 and later import it fine as this was fixed in 426383bde9. The issue still exists in Blender 2.83.9, so the fix would be a candidate for a future corrective release CC @mont29

Since this is fixed in current versions of Blender, I'm closing this as resolved.

Blender 2.90.1 and later import it fine as this was fixed in 426383bde9. The issue still exists in Blender 2.83.9, so the fix would be a candidate for a future corrective release CC @mont29 Since this is fixed in current versions of Blender, I'm closing this as resolved.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#76768
No description provided.