Blender 3.0 cannot import FBX (containing more than 8 UV layers) #93541
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
10 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#93541
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?
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79
Blender Version
Broken: version: 3.0.0 Release Candidate, branch: master, commit date: 2021-11-30 10:50, hash:
blender/blender@4b971bb87cWorked: 2.93.0 - 2.93.7
Caused by blender/blender@04b4ec7889
Short description of error
Blender 3.0 cannot import some Mixamo animations. But Blender 2.93 does it right.
Apparently the issue is related to the amount of UV maps.
Exact steps for others to reproduce the error
Just try to import the fbx I attached (excuse me for the file size)
Walking.fbx
Added subscriber: @carlosmu
blender/blender#95077 was marked as duplicate of this issue
blender/blender#94941 was marked as duplicate of this issue
blender/blender#94485 was marked as duplicate of this issue
#94343 was marked as duplicate of this issue
blender/blender#94236 was marked as duplicate of this issue
blender/blender#94138 was marked as duplicate of this issue
blender/blender#94007 was marked as duplicate of this issue
blender/blender#93912 was marked as duplicate of this issue
blender/blender#93897 was marked as duplicate of this issue
blender/blender#93823 was marked as duplicate of this issue
#93221 was marked as duplicate of this issue
Added subscriber: @PratikPB2123
Added subscriber: @HectorDeAnda
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @deadpin
Technically the older versions are also broken a bit. The model contains 9 UV maps which exceeds the blender limitation of 8 for a given mesh. With older versions only the first 8 UV maps were imported and the rest were dropped. In new blender versions this situation is now surfaced as an Error.
I'll put together a patch a bit later to get back to the previous behavior at least. The addon didn't change but it looks like blender itself now surfaces the error and the addon was not expecting that. We may want another option to still fail on this type of error but I'll see what comes up during the review.
Awesome! Thanks!
I think the best thing would be to import it anyway and warn that some data was not loaded correctly.
Added subscriber: @lichtwerk
Oops, that was caused by blender/blender@04b4ec7889
Blender 3.0 cannot import some Mixamo animations.to Blender 3.0 cannot import FBX (containing more than 8 UV layers)Added subscriber: @JulienDuroure
Probably also an issue for glTF importer
This issue was referenced by blender/blender@c37cd35469
This issue was referenced by blender/blender@7c4fc5b58d
Changed status from 'Confirmed' to: 'Resolved'
Added subscribers: @RichardLyons, @iss
Added subscriber: @mangray
Would this be merged into 3.0.1 or do we have to wait for 3.1? Thanks!
blender/blender@7c4fc5b58d is already on the list for 3.0.1 (if it comes out, but I would guess so), see blender/blender#93479 (3.0 Potential candidates for corrective releases)
Added subscriber: @TinyNick
Added subscriber: @JanErik
Added subscriber: @TodorNikolov
Added subscriber: @CRYELLS
Added subscriber: @paddygaunt
This change looks like it's been approved and committed but the 3.0.0 stable daily build still doesn't work. I have to install 3.1 alpha.
Which is alpha.
Therefore not stable!!
Is there a reason for this? What is the logic behind producing a stable daily build, which claims to include "cool bug fixes", if it doesn't include bug fixes? Have I missed something?
Added subscriber: @DAU
Added subscriber: @thisisadrian12
Added subscriber: @MercySinned
Added subscriber: @clairedignam
Added subscriber: @isaiahbonzi