Collada/Mixamo Importing Bug. #39099

Closed
opened 2014-03-10 22:03:18 +01:00 by Harry Boltz III · 12 comments

System Information
Win7, Mac OSX, ATI Radeon HD 5700 Series

Blender Version
Broken: 2.65, 2.70
Worked: 2.49

Short description of error

Users have experienced a problem with importing certain Mixamo characters into blender while using the Collada format. Its been noted that these characters are usually made of multiple meshes, and these submeshes have multiple joints deforming the mesh. This means that submeshes with a singular joint skinning information (swords, shields, eyes) remain unaffected. These problems are also apparent while trying to bring in a file with animation as opposed to one with just a skeletal hierarchy.

Attached is an example .dae(demo_error_1.dae) with the problem shown. The walk cycle was created via Maya using the Mixamo workflow, and it successfully imports back into Maya without any problem. However, upon trying to bring the file into Blender, blender receives an error and will not bring neither the mesh nor the skeleton into the application.

Having talked with /Nathan, he mentioned that creating a bug log would be helpful. demo_error_1 is the scene as is straight from export. This scene created demo_error_1.txt log, which made the error sound like a text/material problem.

With this knowledge, I modified the mesh of demo_error_1's character to share one brand new diffuse texture, and I saved the new collada as demo_error_2.txt. Importing this new file into blender gave the log demo_error_2.txt.

Exact steps for others to reproduce the error

(I received the log.txt's by opening Blender via cmd and exporting log file to my c:\tmp folder. Not a necessary{F80576} step to get the bugs, but I guess it is to see the exact logs.)

  1. Open Blender 2.7
  2. Import either Mesh.

Files
ColladaBug.zip

**System Information** Win7, Mac OSX, ATI Radeon HD 5700 Series **Blender Version** Broken: 2.65, 2.70 Worked: 2.49 **Short description of error** Users have experienced a problem with importing certain Mixamo characters into blender while using the Collada format. Its been noted that these characters are usually made of multiple meshes, and these submeshes have multiple joints deforming the mesh. This means that submeshes with a singular joint skinning information (swords, shields, eyes) remain unaffected. These problems are also apparent while trying to bring in a file with animation as opposed to one with just a skeletal hierarchy. Attached is an example .dae(demo_error_1.dae) with the problem shown. The walk cycle was created via Maya using the Mixamo workflow, and it successfully imports back into Maya without any problem. However, upon trying to bring the file into Blender, blender receives an error and will not bring neither the mesh nor the skeleton into the application. Having talked with /Nathan, he mentioned that creating a bug log would be helpful. demo_error_1 is the scene as is straight from export. This scene created demo_error_1.txt log, which made the error sound like a text/material problem. With this knowledge, I modified the mesh of demo_error_1's character to share one brand new diffuse texture, and I saved the new collada as demo_error_2.txt. Importing this new file into blender gave the log demo_error_2.txt. **Exact steps for others to reproduce the error** (I received the log.txt's by opening Blender via cmd and exporting log file to my c:\\tmp folder. Not a necessary{[F80576](https://archive.blender.org/developer/F80576/ColladaBug.zip)} step to get the bugs, but I guess it is to see the exact logs.) 1. Open Blender 2.7 2. Import either Mesh. **Files** [ColladaBug.zip](https://archive.blender.org/developer/F80577/ColladaBug.zip)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @heboltz3

Added subscriber: @heboltz3

Removed subscriber: @heboltz3

Removed subscriber: @heboltz3
Gaia Clary was assigned by Bastien Montagne 2014-03-10 23:40:27 +01:00

Added subscriber: @mont29

Added subscriber: @mont29

Gaia, care to check this one? Thanks! :)

Gaia, care to check this one? Thanks! :)

Added subscriber: @heboltz3

Added subscriber: @heboltz3

I was wondering about the status of this bug? Since posting we have been flooded with reports of this breaking workflow. We are desperately seeking a fix.

I was wondering about the status of this bug? Since posting we have been flooded with reports of this breaking workflow. We are desperately seeking a fix.
Member

Added subscriber: @jesterking

Added subscriber: @jesterking
Member

Joining the bug report

Joining the bug report

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Added subscriber: @Sergey

Added subscriber: @Sergey
We currently don't have collada maintainer, moving to TODO http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Import_Export#Import:_Bugs
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
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
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#39099
No description provided.