Collada Import & Export
Wed, Nov 15
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.
Tue, Nov 14
Wed, Nov 8
Sat, Nov 4
If I pack external data, it no longer crashes.
You have to import, then export > crash.
If you import, pack, export, > no crash.
Fri, Nov 3
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?
If possible can you try to find a super simple example that demonstrates the failure in 2.78.5 but works in the 2.78 release? Then provide the blend and 2 collada files, one that works (exported from 2.78) and one that is broken (exported from 2.78.5). Then it is much easier to inspect the model and see what has gone wrong.
Jul 16 2017
@Gaia Clary (gaiaclary) I bet that one is for you ;)
Jul 15 2017
Jul 4 2017
Fixed. Thank you.
Jun 29 2017
Thanks for the report, but no bug here, python API is designed to be efficient, not to protect the developer against himself. There are billions of ways of generating a corrupted mesh from python in Blender, it's up to you to do valid things (and you can always also use Mesh.validate() method in case you do not trust your generated geometry for some reasons, e.g. when importing from other formats).
Jun 25 2017
Thanks you for the report and the patch.
However i believe this issue has been fixed already a while back.
I just checked that specularity is treated correctly now.
This issue is a bit odd. The root object is an Empty with scale and rotation.
The armature and its children are parented to that root empty.
This has been implemented with commit 51d4743033a39a90e60cdad3dd30ffa834d999de
This has been fixed with commit 89060babbcd6099e0d53cf0164661d11a79369bd
Please can you check if it works for you now?
The Collada exporter now exports mesh geometries as <triangles> when the geometry only contains tris (or is triangulated during export).
@Johannes Horvath (John) Peterson: Thanks for reporting this issue. Please can you check if the fix works for you now?
This issue has been resolved with the commits:
Jun 24 2017
This issue has been resolved with the commits:
Jun 15 2017
i must apologize for being so slow. I have fallen ill but i will resume as soon as i can.
I spent two hours to find out that this was my problem when importing blendshapes in Unity. I'm glad to see somebody already tracked out the problem and made a complete explanation of the problem :)
Jun 9 2017
Well more than a week without reply. Closing due to the policy of the bug tracker.
May 30 2017
May 29 2017
Right now all meshes are exported as polygons, even when triangulated. This is not a bug (as far as i can say) but i think it is more elegant to export triangulated meshes as <triangles>. So i will look at this as well :)
@Gaia Clary (gaiaclary), is that considered a bug from our side? We already have Triangulate option, not sure it's supposed to give <polylist> or <triangles> tho.. Your call here!