Collada Import & Export
Fri, Feb 16
if you refer to this file:
The demo files have been removed, so i can not check if this issue has been resolved or not. Please can you resubmit the missing files, so that i can test again?
This issue is fixed in master. You may want to double check that the problem is fully solved.
Fri, Feb 2
Thu, Feb 1
note to self:
It looks like the export can be done in a straight forward way, see rna_Mesh_calc_tangents().
The FBX exporter does it similar to this:
Thanks for reporting. At the end i found the problem was in the way how the importer handles errors. Your files should now import with warnings about missing images.
Wed, Jan 31
I opened T53966 to collect ideas for how to support group instances in a good way.
According to Collada the Node library is used for organizing scenes with many objects into manageable subgroups (see citations at bottom of page). If i understand correct, then your request introduces one library Node per instance_geometry. This adds one level of hierarchy to the exported data:
The Collada specification allows for diffuse color either a texture or a solid color:
Fri, Jan 26
thanks to dfelinto for helping me with this one :)
Wed, Jan 24
Jan 1 2018
Right after importing the fbx the active UV Layer seems to be not defined for the imported Mesh Object. The active UV Layer is automatically enabled as soon as i open the data properties of the mesh object. From this moment on the Collada exporter works without crashing.
same with me
- import fbx and export dae, will crash blender
- export to other file type, it is ok
- save and reopen blender then export dae, it work ok
- daily build blender has same problem
Dec 14 2017
Nov 15 2017
can confirm, seems like a null deref in the collada exporter, @Gaia Clary (gaiaclary) mind taking a look here?
I can confirm crash on windows 10, blender crash during collada export when there is more than one shapekey.
Nov 14 2017
Nov 8 2017
Nov 4 2017
If I pack external data, it no longer crashes.
You have to import, then export > crash.
If you import, pack, export, > no crash.
Nov 3 2017
Please can you create a blend file that will crash blender when you try to export it to dae ?
Then prepare the blend file such that all i need to do is calling:
Happens here on OSX as well. Oct 24 build.
crash log here:
Sep 18 2017
It looks like this problem has been in blender for a while I just found another report that I didn't find on my initial search here.
Sep 15 2017
If you are only going to look at one even thou both have the bug I would prefer you to look at fbx as that's the format I am using as I am uploading to sansar.
Sep 14 2017
The exporters actually don't get prepared stuff from Blender, but cherry pick their information as necessary :) So if you see the same issue with FBX and Collada then this is most probably just a coincidence.
ok its an export issue then I just noticed it happens on import too that's all .
And was trying to give you all the info.
Check our reporting rules, one of them is 'one issue per report', and collada and FBX are definitively totally different issues. We cannot manage confusing reports, handling god ones already eats tremendous of time not spent on actually coding new useful stuff for Blender…
There is a problem 100% I cant explain it any better than I already have so I wont be making another report .If you cant be bothered to do a simple test as I have outlined above then I will just have to find another 3d app to use. All I wanted to do is bug report this not get loads of pedantic replies.
Jul 18 2017
I just downloaded the most recent build, and your fix worked! Thanks so much for solving the issue, I'm really looking forward to using Blender thanks to you!
I'm really new to Blender so I hope I'm following the correct steps to grab the latest build with your fix implemented.
Jul 17 2017
Thanks for reporting and helping to solve this issue by providing the extra demo files!
I believe that i have fixed the animation curve export issue. Please can you check that all is ok now and report back when it still fails?