Hi,
this is my first destruction test, only one mdl/entity is used:
[video:youtube]http://www.youtube.com/watch?v=_vFKY6M_Qjo[/video]

What I did:
- I used a pre sliced mdl, so no realtime slicing at the moment.
- vertex parts of the mdl are moved by realtime generated PhysX boxes.
- also possible with ConvexMeshes, however they are slower to create.

TODO:
- generate realtime slicing of a mdl.
- intelligent dividing algorithm.

I will continue my work in a week, at the moment I have to finish a project, so the release of pXent Pro will be in November!

Why I tryed to do that with lite-c.
I made a Ragdollhaus, but it looked crapy and didn`T work

well, with pXent Pro it will probably work.

maybe it should be a feature...
you can tell a model to be destructable by realtime slicing, or by pre-slicing (I can imagine somethings you always want to have broken in a certain way... for example structural pillars of a building etc.

Other then that it all looks amazing!
I cant wait for the softbodies, it's something i definatly want for my game! (waiting for that to come out before i can continue really xD)

keep it up, i'll buy it day one it comes out!

regards,

is pXent Pro a new code languege, or do you use it like newton lite-c?

pXent (Pro) is a DLL plugin for 3DGS and is written in c++.

... I will make two modes: one for presliced entities and the second in realtime. I am planning to use bmaps as slicing structure, so you can have a kind of heightmap, that says how the entity gets sliced.

Can you elaborate on that a bit more?
Does this mean we can setup the resolution of the slices using bitmaps (big chunks with low res map, smaller chunks with higher res)? or can we colour what needs to break easier then the other (so you can have different materials in a model, like wood and metal for example)?
and how do we apply the bitmap data to a specific model? through it's 2nd skin (which means we couldnt use the shadowmaps for that anymore)?

I'm really excited about it, dont get me wrong, just trying to think one step further and foresee problems that might occur

regards,

Awesome work!. Can't wait for the final version.
Works only with static meshes, or dynamic too?

How much will it cost?
How are the physic objeckts writen?
Is it the same like in lite-c?;

action ball()
{
phent_settype(my,PH_RIGID,PH_SPHERE);
phent_setmass(my,1,PH_SPHERE);
phent_setfriction(my,90);
phent_setelasticity(my,75,100);
phent_setdamping(my,30,5);
ph_setgravity(vector(0,0,-500));
}

or how would it look lick with pXent Pro?

Can't wait!
I realized that I need some nice physics engine in my project, so try to release it soon