Hello,
For a robot simulation project we tried the ColladaDemo example. It runs well but if we import the Collada scene in Blender and then export it, even without change, ColladaDemo then segfault (segfault comes from glibc). We are under Linux 32/64, Blender 2.48 and Bullet 2.74.
Is there specific option for export to Collada in Blender ?
Does anyone encountered the same problem ?
Is there another file format to import scene in Bullet from Blender ? (we tried Quake BSP, but it is not really reliable too).
Thanks.
Clarus, iXce and Myrhev.
Collada Demo import and Blender export -> seg fault
-
- Posts: 2
- Joined: Mon Apr 06, 2009 4:27 pm
-
- Site Admin
- Posts: 4221
- Joined: Sun Jun 26, 2005 6:43 pm
- Location: California, USA
Re: Collada Demo import and Blender export -> seg fault
Can you share the .blend and COLLADA .dae file? Please zip both and attach it to this topic (the forum allows attachments under 10Mb size)For a robot simulation project we tried the ColladaDemo example. It runs well but if we import the Collada scene in Blender and then export it, even without change, ColladaDemo then segfault (segfault comes from glibc). We are under Linux 32/64, Blender 2.48 and Bullet 2.74.
We have a prototype blendreader that can read a .blend file directly, and create Bullet rigid bodies and collision shapes. It will be released for next Bullet release, in the Bullet/Extras/readblend folder.
Thanks,
Erwin
-
- Posts: 2
- Joined: Mon Apr 06, 2009 4:27 pm
Re: Collada Demo import and Blender export -> seg fault
Re,
We solved the problem : we didn't save in a .blend the jenga.dae imported file so when we exported back to a .dae collada the associated .blend reference was not here. And an empty reference made it segfault
Thanks for this fast answer.
We solved the problem : we didn't save in a .blend the jenga.dae imported file so when we exported back to a .dae collada the associated .blend reference was not here. And an empty reference made it segfault

Thanks for this fast answer.