Real-Time Physics Simulation Forum

Re: serialization differences depending on Blender build

2012-08-24T21:04:39+00:00

I am told the changes to Bullet in r2542 have helped our issues when reading .bullet files. Thanks again!

Statistics: Posted by cyrfer — Fri Aug 24, 2012 9:04 pm

Re: serialization differences depending on Blender build

2012-08-01T18:55:29+00:00

Actually, if I now understand the diff from the patch, the fixes were only in READING the .bullet file. Hopefully, I can test this fix in my code without a new Blender build. Will get back to you on this...

Statistics: Posted by cyrfer — Wed Aug 01, 2012 6:55 pm

Re: serialization differences depending on Blender build

2012-08-01T20:57:59+00:00

Thank you for the fix! The diff looks like a great improvement. I hope to test it soon with Sergej's help.
http://code.google.com/p/bullet/issues/ ... id=618#c15

Here is the bug report for Blender.
http://projects.blender.org/tracker/?fu ... group_id=9

One thing that may hold back Blender from using this fix is that Bullet does not have a new release. Will there be a new release soon? I know they are trying to release around SIGGRAPH time, but that may be sliding...

PS. Will you be attending? I'll be there!

Statistics: Posted by cyrfer — Tue Jul 31, 2012 11:55 pm

Re: serialization differences depending on Blender build

2012-04-05T17:30:04+00:00

Thanks for looking into this issue, reported as Issue 618.
John

Statistics: Posted by cyrfer — Thu Apr 05, 2012 5:30 pm

Re: serialization differences depending on Blender build

2012-04-05T15:41:43+00:00

This should not happen, Bullet serialization was designed to solve 32bit/64bit, endianness and versioning issues.

Can you file an issue in the Bullet tracker (http://code.google.com/p/bullet/issues/list) with
1) Blender full version info
2) attach the .blend file
3) attach the .bullet file that causes problems?
Thanks a lot,
Erwin

Statistics: Posted by Erwin Coumans — Thu Apr 05, 2012 3:41 pm

[resolved] serialization differences depending on Blender

2012-08-24T21:05:10+00:00

Hi,
I'm using the technique to export a Bullet file (the scene has static objects, dynamic rigid body objects, and ragdolls) from within the Blender Game Engine via a keyboard controller hooked up to my export script. This process seems to work pretty well, with one issue.

I am seeing slightly different results when using Blender-64 or Blender-32. I suspect the issue is in the Bullet serialization. When my 32 bit application loads the Bullet file exported from Blender 32 bit on a 32 bit PC, I see no problems. If I use the same Bullet file (still from 32 bit Blender) on a 64 bit PC with my 32 bit application, I see bad floating point values (e.g. -1.#IND) for at least one of the ragdoll objects (btCollisionObject has a bad m_basis in its m_worldTransform).

All these tests are in Windows.

I am in the process of testing an export with 64 bit Blender for my 64 bit PC (with 32 bit application). I will post back with these results later today.
Where might this difference be coming from? Is it Bullet serialization or deserialization or both? Has anyone else experienced this?

I found that I need to use a 32-bit build of Blender to export a file. I performed this on my 64-bit PC, but I'm not sure if the platform is important.

Thanks for any tips!

Statistics: Posted by cyrfer — Wed Apr 04, 2012 6:47 pm