Credits: All bullet physics and bulletsharp devvvvs.
Bullet physics nodes first release.
Still beta, but fairly stable. Some breaking changes are to be expected in upcoming releases.
Work on beta 25+ only (Latest version for beta26)
Still on the todo list:
In the mean time, have fun.
it looks great!
wow, hard without any help...
@kalle: there's 1 help file, read it :)
What's in the box?
Will only tell to the winner :)
have to start a thread about the bugs, 'cause i can't0 attach files here...
ahhaha nice contest man! great idea!
OMG Dude, you are evil with this one!! Will try my best and figure it out.
Going to download Se7en again to get jn the mood...
New release with the following:
Removed 0.5.0, replaced by 0.5.1
Contact details back again, bulletsharp was disposing bodies without my consent :)
vux, a minimal hint: you should drag the links to reverse the order
Bullet-0.4.2.zip - 12.01.1120:12 UTC by vux | 67 downloads
Bullet-0.5.1.zip - 14.01.1102:36 UTC by vux | 30 downloads
Bullet-0.5.3.zip - 16.01.1101:46 UTC by vux | 26 downloads
Bullet-0.5.6.zip - 18.01.1121:06 UTC by vux | 10 downloads
so the latest is up and appear in the "download latest revision" link. That's why the trend is going down, 67 30 26 10 downloads for a such GREAT contribution ?!?
Ah yeah good point, done now :)
Heightfield is perfect now! Nice.
What happened to the 31st January help files?
interesting question :D
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.
Ends on 31th of January, then will release help patches.
rhaaa, didn't realize it would be 2012 ! :)
Can't wait to see some help patches, I'm struggling to make anything move at all, I might be missing something obvious/basic/logical.
Can anyone help ?
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:
There's also this, which is pretty basic:
All the best,
Hey thanks a lot Lightmare, this is super useful !
Congrats to vux, just played around with this for an hour, this is plain awesomeness !!
is there any helppatch around?
can't bless vux enough for updating this!
aah the 0.5.7 update was a real life-saver!
and as good news, I heard flateric working on some girlpower samples :)
Bug when object is destroyed, whole scene is frozen for a frame.
Very stable otherwise.
have to disable the main renderer for one frame when destroying an object
anonymous user login