wow, hard without any help...

@vux. cool, but feel myself a bit like this guys

Will only tell to the winner :)

ahhaha nice contest man! great idea!

New release with the following:

• Custom string output in rigid body details fixed (was not outputting).
• SpreadMax calculation in rigid convex hull was wrong.
• Rigid Shapes now have custom string.
• New node: GetRigidShapeDetails.
• Collision Objects can now have a second arbitrary object as custom pin (must implement ICloneable).
• CreateRigidBody/UpdateRigidBody now features Allow Sleep/Is Active option
• CreateBody also features Static/Kinematic flag.
• CreateRigidBody (Persist version) was not cleaning list on world reset.
• GetContactDetails is temporarily removed as there's a potential crash using it, will be added back soon.

Removed 0.5.0, replaced by 0.5.1
Contact details back again, bulletsharp was disposing bodies without my consent :)

0.5.6 Update:

• ApplyForce/Torque/Impulse now have autoactivate option (default true), so you can wake up sleeping bodies.
• Raycast now outputs Full body type, and output is now done by query index.
• UpdateBody now have Position/Set Position (for kinematic use)
• Heightfield is now scaled and centered correctly.

Ah yeah good point, done now :)

What happened to the 31st January help files?

:)

Hello, Mr Vux,

I wanted to let you know about something I experienced while experimenting with the Bullet Physics nodes a week ago.

I created an inert box to act as the ground surface. It was kind of pizza-box shaped, meaning it was rather flat. If I drop another object from a fairly high position, I would expect it to bounce back up, when it hits the box, but it would fall through it.

Now it seems to me that for collision detection, you use the current position of an object, to see if it intersects with another object. The problem is - because the calculations are inherently discrete - that if an object has a high velocity, the next calculated position might be at the other side of the object. So I think one should check if the line between previous position and current position intersects with another object. If it does, the 2 objects collide.

Anyway, that's what I suspect to be the reason of this unexpected behaviour.

Cheers.

Hi Joanie

have a look at the attached patch, it's not well documented but makes use of quite a few of the nodes, there's still some nodes I just haven't tried yet but hopefully this helps.

...I've failed at finding the attach file button so here's a dropbox link:

http://dl.dropbox.com/u/502753/Bullet.v4p

There's also this, which is pretty basic:

bullet-+-irrklang-demo

All the best,

Joseph

is there any helppatch around?

aah the 0.5.7 update was a real life-saver!

very good. i have only hard patches, but i want to try some force fields stuff
but needs help patch attracting point still in work tho...