Blender 3.0 cannot import FBX (containing more than 8 UV layers) #93541

Closed
opened 2021-12-01 15:47:40 +01:00 by Carlos Muñoz · 40 comments

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@4b971bb87c
Worked: 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

imagen.png

**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@4b971bb87c` Worked: 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](https://archive.blender.org/developer/F12673454/Walking.fbx) ![imagen.png](https://archive.blender.org/developer/F12673442/imagen.png)
Author

Added subscriber: @carlosmu

Added subscriber: @carlosmu

blender/blender#95077 was marked as duplicate of this issue

blender/blender#95077 was marked as duplicate of this issue

blender/blender#94941 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

blender/blender#94485 was marked as duplicate of this issue

#94343 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#94236 was marked as duplicate of this issue

blender/blender#94138 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#94007 was marked as duplicate of this issue

blender/blender#93912 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#93897 was marked as duplicate of this issue

blender/blender#93823 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

#93221 was marked as duplicate of this issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Added subscriber: @HectorDeAnda

Added subscriber: @HectorDeAnda
Member

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

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

Added subscriber: @deadpin

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.

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.
Author

Awesome! Thanks!
I think the best thing would be to import it anyway and warn that some data was not loaded correctly.

Awesome! Thanks! I think the best thing would be to import it anyway and warn that some data was not loaded correctly.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Oops, that was caused by blender/blender@04b4ec7889

Oops, that was caused by blender/blender@04b4ec7889
Philipp Oeser self-assigned this 2021-12-02 15:48:16 +01:00
Philipp Oeser changed title from Blender 3.0 cannot import some Mixamo animations. to Blender 3.0 cannot import FBX (containing more than 8 UV layers) 2021-12-02 16:17:51 +01:00
Member

Added subscriber: @JulienDuroure

Added subscriber: @JulienDuroure
Member

Probably also an issue for glTF importer

Probably also an issue for glTF importer

This issue was referenced by blender/blender@c37cd35469

This issue was referenced by blender/blender@c37cd3546904ce73ad57f9de73427a585c583b12

This issue was referenced by blender/blender@7c4fc5b58d

This issue was referenced by blender/blender@7c4fc5b58d2e7982aefbba093cb8f1dc36b64884

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'

Added subscribers: @RichardLyons, @iss

Added subscribers: @RichardLyons, @iss

Added subscriber: @mangray

Added subscriber: @mangray
Author

Would this be merged into 3.0.1 or do we have to wait for 3.1? Thanks!

Would this be merged into 3.0.1 or do we have to wait for 3.1? Thanks!
Member

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)

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: @TinyNick
Member

Added subscriber: @JanErik

Added subscriber: @JanErik
Member

Added subscriber: @TodorNikolov

Added subscriber: @TodorNikolov

Added subscriber: @CRYELLS

Added subscriber: @CRYELLS

Added subscriber: @paddygaunt

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?

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?
Member

Added subscriber: @DAU

Added subscriber: @DAU
Member

Added subscriber: @thisisadrian12

Added subscriber: @thisisadrian12

Added subscriber: @MercySinned

Added subscriber: @MercySinned
Member

Added subscriber: @clairedignam

Added subscriber: @clairedignam

Added subscriber: @isaiahbonzi

Added subscriber: @isaiahbonzi
Sign in to join this conversation.
No Milestone
No project
No Assignees
10 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#93541
No description provided.