Tiny little feature i did add to SVN just before freeze.
video on youtube
blend is there
http://mosebjorn.altervista.org/more/
have fun
BM
Tiny little feature i did add to SVN just before freeze.
video on youtube
So that would mean we would be able to simulate the new memory materials now in labs.
Nice work.
That would mean: only a few chosen members of the magic circle
/* those who
*dived deep in the magics of mass-spring systems
*know all the magic of newtons laws
*know the magic button
*/
will ever be able to use that without being struck by the wrath of the big bad physicist which is lurking here.
It could perhaps simulate tinfoil or any metal after some sort of impact. Would be interesting to see what people come to use it for.
a car crashing into a wall.
Bjorn, awesome dude! <runs to update wiki>
it is possible in the future to animate the spring values and other settings over time ((via IPO)? Could have a thing smash, then quickly at some later point pop back into shape. Or melt. or have gravity and then not. lose mass. Cloth had a few good ideas: edit shapes to fix minor errors? protect cache up to certain points in time?
I did not code it, but I know that some soft body variables are exposed to python.
So i think most of the effects described should be possible with a bit of scripting.
Yes editing the cache to iron out flaws is a nice feature. But i will wait until Daniel has finished that to ‘steal’ mature code.
Bad thing about point cache is that it does not store all the information to resume (e.g velocities). You can try:
*Let a cube fall
*Break the simulation
*Restart
At the interrupted frame the cube will start to fall with zero speed again.
Until that issue is resolved i don’t see the use of partly protected cache.
At the moment i think about ways reconstructing missing information from the particle path in time.
BM
yes, good point, each vertex should be saved as a vector, not a point. Actually, not just a vector, but a location and speed vector and acceleration vector.