Collada Cannot Import #39379

Closed
opened 2014-03-24 02:15:01 +01:00 by Hikmet Koyuncu · 17 comments

System Information
Operating system and graphics card

Windows 7 Ultimate 64-bit, Intel HD 3000

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
2.7
Worked: (optional)

Short description of error
Collada Import process is so slow. And sometimes impossible.
I attached example file. I imported in 3dsmax, only 15-20 seconds, but in Blender
cannot import after 20 minutes, and still waiting... Collada is unique animation
transfer format in Blender, so most important for me (and for most peoples).

FFX_Yuna.7z

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

**System Information** Operating system and graphics card Windows 7 Ultimate 64-bit, Intel HD 3000 **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) 2.7 Worked: (optional) **Short description of error** Collada Import process is so slow. And sometimes impossible. I attached example file. I imported in 3dsmax, only 15-20 seconds, but in Blender cannot import after 20 minutes, and still waiting... Collada is unique animation transfer format in Blender, so most important for me (and for most peoples). [FFX_Yuna.7z](https://archive.blender.org/developer/F82348/FFX_Yuna.7z) **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps
Author

Changed status to: 'Open'

Changed status to: 'Open'
Hikmet Koyuncu self-assigned this 2014-03-24 02:15:01 +01:00
Author

Added subscriber: @spiderh

Added subscriber: @spiderh
Hikmet Koyuncu was unassigned by Bastien Montagne 2014-03-24 08:14:55 +01:00
Gaia Clary was assigned by Bastien Montagne 2014-03-24 08:14:55 +01:00

Added subscriber: @mont29

Added subscriber: @mont29

Gaia, care to check? Thanks! :)

Gaia, care to check? Thanks! :)

Added subscriber: @padone

Added subscriber: @padone

Hikmet, I don't know if this may help .. but have you tried to load your model in Autodesk FBX Viewer ?

I did it and your scene seems quite strange, see the picture below. Is it on purpose ? I mean, is it the intended appearence your scene should have ?

If the FBX Viewer itself can't read the scene correctly then I doubt Blender can. This could be a sort of "proof test" you could use to test your exports before passing them to Blender.

Yuna.jpg

Hikmet, I don't know if this may help .. but have you tried to load your model in Autodesk FBX Viewer ? I did it and your scene seems quite strange, see the picture below. Is it on purpose ? I mean, is it the intended appearence your scene should have ? If the FBX Viewer itself can't read the scene correctly then I doubt Blender can. This could be a sort of "proof test" you could use to test your exports before passing them to Blender. ![Yuna.jpg](https://archive.blender.org/developer/F82717/Yuna.jpg)
Author

No, I imported in 3dsmax 2013 and didn't seem problem, because I used OpenCollada plugin. FBX Viewer cannot read OpenCollada format very well.

No, I imported in 3dsmax 2013 and didn't seem problem, because I used OpenCollada plugin. FBX Viewer cannot read OpenCollada format very well.

Hikmet,

I tested your scene against the official collada coherency test. It reports a series of errors, I extracted some of them for your reference.

Unfortunately the fact that Max reads the scene does not mean that it is good for other applications to read. This is what I was trying to tell in my previous post. You should check your exports against a reference viewer to see if it is good or not. Since afaik there's not such a viewer around, the Autodesk viewer seems a decent choice. Also, the coherency test is useful to check if your export works well.

For example, from what I can understand from the last error reports, you have absolute paths for the textures, so they can't be found in any other platform apart your own. This is a typical export error you should check for.

For the sake of completeness, I would add that none of the reported errors in the scene seems critical, so a good importer may be able to handle them anyway. But checking your exports is always a good thing.

Hope this helps. Bye :)

http://collada.org/public_forum/showthread.php/434-coherency-test-available

ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}texture', attribute 'texcoord': '' is not a valid value of the atomic type 'xs:NCName'.
ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00Pos' is not a valid value of the atomic type 'xs:NCName'.
ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00Nrm' is not a valid value of the atomic type 'xs:NCName'.
ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00UV' is not a valid value of the atomic type 'xs:NCName'.
ERROR: CHECK_file failed, file:/E:/Programlar%20-%20Duzenlenmis/Game%20Programs/Tools/_General/3D%20Programs/Noesis%204.0972/Program/Package/ffx0000 not found
ERROR: CHECK_file failed, file:/E:/Programlar%20-%20Duzenlenmis/Game%20Programs/Tools/_General/3D%20Programs/Noesis%204.0972/Program/Package/ffx0001 not found

Hikmet, I tested your scene against the official collada coherency test. It reports a series of errors, I extracted some of them for your reference. Unfortunately the fact that Max reads the scene does not mean that it is good for other applications to read. This is what I was trying to tell in my previous post. You should check your exports against a reference viewer to see if it is good or not. Since afaik there's not such a viewer around, the Autodesk viewer seems a decent choice. Also, the coherency test is useful to check if your export works well. For example, from what I can understand from the last error reports, you have absolute paths for the textures, so they can't be found in any other platform apart your own. This is a typical export error you should check for. For the sake of completeness, I would add that none of the reported errors in the scene seems critical, so a good importer may be able to handle them anyway. But checking your exports is always a good thing. Hope this helps. Bye :) http://collada.org/public_forum/showthread.php/434-coherency-test-available ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}texture', attribute 'texcoord': '' is not a valid value of the atomic type 'xs:NCName'. ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00Pos' is not a valid value of the atomic type 'xs:NCName'. ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00Nrm' is not a valid value of the atomic type 'xs:NCName'. ERROR: CHECK_schema Error msg=Element '{http://www.collada.org/2005/11/COLLADASchema}source', attribute 'name': '0000_object00UV' is not a valid value of the atomic type 'xs:NCName'. ERROR: CHECK_file failed, file:/E:/Programlar%20-%20Duzenlenmis/Game%20Programs/Tools/_General/3D%20Programs/Noesis%204.0972/Program/Package/ffx0000 not found ERROR: CHECK_file failed, file:/E:/Programlar%20-%20Duzenlenmis/Game%20Programs/Tools/_General/3D%20Programs/Noesis%204.0972/Program/Package/ffx0001 not found
Author

Thanks for reply padone.

I'm use OpenCollada plugin for 3dsmax: https://collada.org/mediawiki/index.php/OpenCOLLADA

Exporter don't export texture data very well, but animation data exported perfect. I retextured model after import. I'm use same exporter for small files and Blender import this files, but very slowly. If animation data a bit long, then cannot import (wait for long long time).

Problem is Blender's Collada importer very very slow. Source code must check and optimize.

Thanks for reply padone. I'm use OpenCollada plugin for 3dsmax: https://collada.org/mediawiki/index.php/OpenCOLLADA Exporter don't export texture data very well, but animation data exported perfect. I retextured model after import. I'm use same exporter for small files and Blender import this files, but very slowly. If animation data a bit long, then cannot import (wait for long long time). Problem is Blender's Collada importer very very slow. Source code must check and optimize.
Member

Added subscriber: @jesterking

Added subscriber: @jesterking
Member

Subscribing :)

Subscribing :)
Member

@spiderh, could you attach some screenshots of how it should look like? And if possible a rendered animation would help too, so end result in Blender, when fixed, can be verified.

@spiderh, could you attach some screenshots of how it should look like? And if possible a rendered animation would help too, so end result in Blender, when fixed, can be verified.
Author

Hi!

Here are example Collada file (633 frame, It took 40 seconds for import).

Yuna_633_fix_image_path.7z

And screenshots:

x100 scale, rotate 180 degree on X axis.

01_-Yuna-633_frame-First_Import-x100_scale-_rotate_x_180.png

x400 scale, rotate 180 degree on X axis.

02_-Yuna-633_frame-First_Import-x400_scale-rotate_x_180-_fix_image_paths.png

x400 scale, rotate 180 degree on X axis. Fix Materials (Alpha, Specular etc...)

03_-Yuna-633_frame-First_Import-x400_scale-rotate_x_180-_fix_image_paths_fix_mats.png

My first uploaded DAE files is 8909 frame.

Here, open same Collada file on Noesis 3D Screenshot (Export from this program. First DAE. 8909 frame)

Yuna_8909_Noesis_Screen.png

Here, this is 3dsMax screenshot (First DAE, 8909 frame, It took 35 seconds for import. No fix material.):

Yuna_8909_3dsmax_Screen.png

Hi! Here are example Collada file (633 frame, It took 40 seconds for import). [Yuna_633_fix_image_path.7z](https://archive.blender.org/developer/F89161/Yuna_633_fix_image_path.7z) And screenshots: x100 scale, rotate 180 degree on X axis. ![01_-_Yuna_-_633_frame_-_First_Import_-_x100_scale_-_rotate_x_180.png](https://archive.blender.org/developer/F89169/01_-_Yuna_-_633_frame_-_First_Import_-_x100_scale_-_rotate_x_180.png) x400 scale, rotate 180 degree on X axis. ![02_-_Yuna_-_633_frame_-_First_Import_-_x400_scale_-_rotate_x_180_-_fix_image_paths.png](https://archive.blender.org/developer/F89171/02_-_Yuna_-_633_frame_-_First_Import_-_x400_scale_-_rotate_x_180_-_fix_image_paths.png) x400 scale, rotate 180 degree on X axis. Fix Materials (Alpha, Specular etc...) ![03_-_Yuna_-_633_frame_-_First_Import_-_x400_scale_-_rotate_x_180_-_fix_image_paths_fix_mats.png](https://archive.blender.org/developer/F89177/03_-_Yuna_-_633_frame_-_First_Import_-_x400_scale_-_rotate_x_180_-_fix_image_paths_fix_mats.png) My first uploaded DAE files is 8909 frame. Here, open same Collada file on Noesis 3D Screenshot (Export from this program. First DAE. 8909 frame) ![Yuna_8909_Noesis_Screen.png](https://archive.blender.org/developer/F89163/Yuna_8909_Noesis_Screen.png) Here, this is 3dsMax screenshot (First DAE, 8909 frame, It took 35 seconds for import. No fix material.): ![Yuna_8909_3dsmax_Screen.png](https://archive.blender.org/developer/F89167/Yuna_8909_3dsmax_Screen.png)
Member

Thanks!

Thanks!

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Added subscriber: @Sergey

Added subscriber: @Sergey

jesty, i'm totally fine if you gonna to improve collada, but in the bug tracker we only keep reports we can tackle in reaosnable time. So IMO it's better to keep collada in own wiki page (http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Import_Export#Import:_Bugs in this case).

You'll be very welcome to fix issues, but if we accept bug reports here you need to become an official maintainer, meaning fixing like at least bug per week ;)

jesty, i'm totally fine if you gonna to improve collada, but in the bug tracker we only keep reports we can tackle in reaosnable time. So IMO it's better to keep collada in own wiki page (http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Import_Export#Import:_Bugs in this case). You'll be very welcome to fix issues, but if we accept bug reports here you need to become an official maintainer, meaning fixing like at least bug per week ;)
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
5 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#39379
No description provided.