Blender does not export to fbx file #105213

Closed
opened 2024-03-04 03:19:57 +01:00 by Pratik Borhade · 3 comments
Member

System Information
Operating system: Linux Mint
Graphics card: RTX 3070 TI

Blender Version

Worked: 4.0.0

Short description of error
FBX export fails

Exact steps for others to reproduce the error
Tried to export character to fbx file.

Blender console output:
Read prefs: "/home/haaken/.config/blender/4.0/config/userpref.blend"
Read blend: "/mnt/2e9a1e9f-2097-408c-ab9a-a01b32f11d28/Hulder/crown-test.blend"

FBX export starting... '/mnt/2e9a1e9f-2097-408c-ab9a-a01b32f11d28/Hulder/crown-test.fbx'
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
(bpy.data.armatures['rig.001'], 'POSE')
Traceback (most recent call last):
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/init.py", line 663, in execute
return export_fbx_bin.save(self, context, **keywords)
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3627, in save
ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod)
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3510, in save_single
fbx_objects_elements(root, scene_data)
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3335, in fbx_objects_elements
fbx_data_texture_file_elements(objects, blender_tex_key, scene_data)
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 1692, in fbx_data_texture_file_elements
elem_props_template_set(tmpl, props, "p_vector_3d", b"Translation", tex.translation)
File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/modules/bpy_extras/node_shader_utils.py", line 803, in translation_get
return self.node_mapping.inputs["Location"].default_value
KeyError: 'bpy_prop_collection[key]: key "Location" not found'

1x6eRrg0YnOqLW-_BbwoMtzKtrs6cKkMW

original report at blender/blender#119030

**System Information** Operating system: Linux Mint Graphics card: RTX 3070 TI **Blender Version** Worked: 4.0.0 **Short description of error** FBX export fails **Exact steps for others to reproduce the error** Tried to export character to fbx file. Blender console output: Read prefs: "/home/haaken/.config/blender/4.0/config/userpref.blend" Read blend: "/mnt/2e9a1e9f-2097-408c-ab9a-a01b32f11d28/Hulder/crown-test.blend" FBX export starting... '/mnt/2e9a1e9f-2097-408c-ab9a-a01b32f11d28/Hulder/crown-test.fbx' (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') (bpy.data.armatures['rig.001'], 'POSE') Traceback (most recent call last): File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/__init__.py", line 663, in execute return export_fbx_bin.save(self, context, **keywords) File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3627, in save ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod) File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3510, in save_single fbx_objects_elements(root, scene_data) File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 3335, in fbx_objects_elements fbx_data_texture_file_elements(objects, blender_tex_key, scene_data) File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/addons/io_scene_fbx/export_fbx_bin.py", line 1692, in fbx_data_texture_file_elements elem_props_template_set(tmpl, props, "p_vector_3d", b"Translation", tex.translation) File "/home/haaken/Nedlastinger/blender-4.0.0-linux-x64/4.0/scripts/modules/bpy_extras/node_shader_utils.py", line 803, in translation_get return self.node_mapping.inputs["Location"].default_value KeyError: 'bpy_prop_collection[key]: key "Location" not found' [1x6eRrg0YnOqLW-_BbwoMtzKtrs6cKkMW](https://projects.blender.org/attachments/24dc1d4a-8ac8-4412-8d64-d3a831ea5e6a) original report at https://projects.blender.org/blender/blender/issues/119030
Pratik Borhade added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-03-04 03:19:57 +01:00

I am getting an identical error also when attempting to export a specific mesh on Blender 4.0.2. This issue does not occur if I delete the mesh and add e.g. a cube within the original blend file (attached) - in that case it exports just fine - so there's something about this specific mesh that it doesn't like.

System info: Windows 10 (19405), RTX 2070 Super, Ryzen 5900X.

stack trace
Python: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\__init__.py", line 663, in execute
    return export_fbx_bin.save(self, context, **keywords)
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3627, in save
    ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod)
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3510, in save_single
    fbx_objects_elements(root, scene_data)
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3335, in fbx_objects_elements
    fbx_data_texture_file_elements(objects, blender_tex_key, scene_data)
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1692, in fbx_data_texture_file_elements
    elem_props_template_set(tmpl, props, "p_vector_3d", b"Translation", tex.translation)
  File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy_extras\node_shader_utils.py", line 803, in translation_get
    return self.node_mapping.inputs["Location"].default_value
KeyError: 'bpy_prop_collection[key]: key "Location" not found'

(second sculpting attempt so the vertices are quite messed up 😭, but this worked on I believe Blender 3.6 Edit: it did work in Blender 3.6, but I also migrated hard drives so that was probably what did it. see below)

I am getting an identical error also when attempting to export a specific mesh on Blender 4.0.2. This issue does not occur if I delete the mesh and add e.g. a cube within the original blend file (attached) - in that case it exports just fine - so there's something about this specific mesh that it doesn't like. System info: Windows 10 (19405), RTX 2070 Super, Ryzen 5900X. <details> <summary>stack trace</summary> ``` Python: Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\__init__.py", line 663, in execute return export_fbx_bin.save(self, context, **keywords) File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3627, in save ret = save_single(operator, context.scene, depsgraph, filepath, **kwargs_mod) File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3510, in save_single fbx_objects_elements(root, scene_data) File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 3335, in fbx_objects_elements fbx_data_texture_file_elements(objects, blender_tex_key, scene_data) File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\addons\io_scene_fbx\export_fbx_bin.py", line 1692, in fbx_data_texture_file_elements elem_props_template_set(tmpl, props, "p_vector_3d", b"Translation", tex.translation) File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy_extras\node_shader_utils.py", line 803, in translation_get return self.node_mapping.inputs["Location"].default_value KeyError: 'bpy_prop_collection[key]: key "Location" not found' ``` </details> (second sculpting attempt so the vertices are quite messed up 😭, ~~but this worked on I believe Blender 3.6~~ Edit: it _did_ work in Blender 3.6, but I also migrated hard drives so that was probably what did it. see below)

Ok in my case it seems like the mesh had a reference to an image which I'm guessing it couldn't find. When I removed the material that was referencing the image and created a brand new one it exported completely fine.

Ok in my case it seems like the mesh had a reference to an image which I'm guessing it couldn't find. When I removed the material that was referencing the image and created a brand new one it exported completely fine.

This should be fixed with blender/blender@0b19f1f4a0

This should be fixed with blender/blender@0b19f1f4a0b1722c212a098715c35cad6b015215
Jesse Yurkovich added
Status
Resolved
and removed
Status
Needs Triage
labels 2024-03-13 05:26:29 +01:00
Blender Bot added
Status
Archived
and removed
Status
Resolved
labels 2024-03-13 05:26:33 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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#105213
No description provided.