(possible bug) & breaking constraints example

Physics APIs, Physics file formats, Maya, Max, XSI, Cinema 4D, Lightwave, Blender, thinkingParticles™ and other simulation tools, exporters and importers
feltstone
Posts: 5
Joined: Sun Jul 30, 2006 7:46 pm
Location: Salt Lake City, UT

(possible bug) & breaking constraints example

Post by feltstone »

Hi All,

I'm new to this forum and new to Blender and ContinuousPhysics so please let me know if I'm posting in the wrong place or what not.

I wanted to share an example of breaking constraints that I've been working on. Here is one of my latest renderings (about a 12 MB download):

http://www.feltstone.com/0001_0580.avi

It is of a sphere crashing down on a collection of cubes that are all tied together with constraints. The forces then break the constraints and the cubes go flying. In this animation you can see some of the cubes sticking together still. The physics are amazing. The cubes still holding together still bounce together and everything.

Here is a zip file of multiple .blend files as examples:

http://www.feltstone.com/constraint_break_examples.zip

It isn't documented yet and still pretty rough. The file "smashy_smashing_not_working.blend" is one I've had trouble getting to work if anyone wants to take a look at that one.

Apparently I altered my original .blend file that goes with the above rendered animation. Here is one close to that one with the physics already rendered to IPO paths if anyone is interested: (18 MB download):

http://www.feltstone.com/smashy_smashy_ ... _paths.zip

Let me know of any questions and hopefully this will be of use to someone. I'm loving this stuff and excited to get involved more.

Thanks!

feltstone
feltstone
Posts: 5
Joined: Sun Jul 30, 2006 7:46 pm
Location: Salt Lake City, UT

little fix with AxisSweep3 constructor

Post by feltstone »

FYI, I fixed my initial crashing problem by altering the AxisSweep3 constructor as follows:

broadphase = new AxisSweep3(worldMin,worldMax, 32766);

The handles were maxing out at 1024 through a default parameter. I'm not sure if 32766 is the best number but I just wanted to try it to see if it worked. Still getting some crashes sometimes when the simulation finishes but at least the sim starts now.

feltstone