FBX Import: Can't import FBX file. AttributeError:'NoneType' object has no attribute 'data' #82830
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#82830
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
System Information
Operating system: Windows-10-10.0.14393-SP0 64 Bits
Graphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15
Blender Version
Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-11-17 22:01, hash:
blender/blender@e580c18853
Worked: 2.79
Short description of error
This is an issue that was closed prior due to unresponsive user that affected 2.82 to the beta version of 2.91.
I tested it on the stable release 2.90.1 as well.
An FBX I attempt to import into Blender fails to load in with the following.
if import_fbx.load(self, context, filepath=path, **keywords) == {'FINISHED'}:
(); del _
fbx_item[1] = blen_read_geom(fbx_tmpl, fbx_obj, settings)
blen_read_geom_layer_color(fbx_obj, mesh)
blen_data = color_lay.data
{F9320007}
{F9320013}
Here I've uploaded two files. The smallest one is a 2015 FBX.
The other one is 2018 FBX.
They both give the same error.
I open Blender, I select everything in viewport, delete, then I import FBX, and import one of the two appended files.
These are my import settings.
https://i.imgur.com/UqJ6Btq.png
Added subscriber: @GeekyGami
Adding details for context, might be useful.
So, I'm using SB3UGS to export FBX from a Unity game.
I'm specifically exporting a skinnedmeshrenderer with its morphs (Blendshapes)
I have an option I can check, for it to export "morph masks"
When that option is checked, and I import the resulting FBX (I.E. one of those two) is when the error occurs.
When it is unchecked, it imports fine.
So, I think this might have something to do with morph masks.
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Confirmed'
The source of the problem is Blender's limit of eight vertex color layers. The file contains more and the
*.fbx
importer doesn't keep track how many have been created before. If the limit is reachedmesh.vertex_colors.new(name=fbx_layer_name, do_init=False)
returnsNone
. The importer should handle this case properly, hence I'm marking this as confirmed.In a cursory check I've noticed that other importers, e.g. PLY, coat3D or X3D don't seem to handle this case properly either. A similar check would also be necessary for UV layers as these have a hard limit as well.
Added subscriber: @Limarest
Tested files with BetterFBX addon - imported correctly and even had the shape keys
@Limarest When including a check for the return value, it imports the file fine as well. Neither the official FBX importer nor a third-party add-on can change the limits though, so only eight vertex color layers will be loaded.
This issue was referenced by
a0e8b8b787
Changed status from 'Confirmed' to: 'Resolved'