Irrlicht Engine

Mhm. I made one some time ago for a quick-and-dirty-test. I needed some properties of a RigidBodyControl so i made one, but it aint good code or anything like comfortable using. But it was patched together in a matter of minutes and maybe you find some inspiration in it? :)

Header:
http://pastebin ...

btConvexShape* hull = new btConvexTriangleMeshShape(triagle);

Change that line to use a BVH, not a ConvexShape.

If you have textures that cant ever mix like grass and stone you can pack those in the same layer with different colors so the shader can decide which texture to use. That way you reduce the amount of layers needed.
But with half way modern hardware thats not needed. I have the crappiest hardware ...

Multilayer splatting for example.

Just by looking on the images i would say your Pivotpoints are wrong.
Pivot point of mesh and rig on the same spot: Alllll right.
Pivot point of mesh and rig on different spots: SPLATTER SPLASH BOOM DIVISION BY ZERO DOOMSDAY. Looks exactly like the problem you got.

( Im not quite expereienced with ...

I hacked around a lot to get some stuff running with Irrbullet recently... And the bullet version is outdated. I tried it with the newest Bullet and it failed to compile due to some changes in bullet...
If i hadnt integrated it so well by now i would totally go for my own wrapper to be honest ...

Maybe you could get Hardware isntancing to work somehow.
http://http.developer.nvidia.com/GPUGem ... ter03.html

They certainly have some nice use cases and can look astonishingly well.
But they have their unique set of horrible traits, too.

Those are the iteration times when it comes to extraction and creation, the memory usage if you save volumes and/or save them to the harddisc ( Runtime length encoding ...

Sorry it took so long, i was kinda ill.
Well. Thats what the shader does on my mesh. Its all a single mesh, pretty dense and the fragment shader is expensive, but it works hilariously good. The result in the screen is a tad weird, since i was trying around with the material-distribution parameters ...

I dont think that he is talking about a voxel based approach here. More an object-based.
I dont beliefe Physx has builtin Voxel support.

For the Voxel approach entirely different designs should be used than for the one-object based approaches.

Vertex layouts have some neat use cases. :)
I'm working on a vertexcollapse algorithm for now, but i will post a screenshot of my a bit more advanced Terrains. The sphere is abit boring. :P

Could take some time tho. I dont know how fast i will finish the VC-algorithm. I hate to operate on those ...

Well then. I went through all the pain of learning how to work with it ( It was quite easy, when i look back... Stupid me did some mistakes at the beginning. )

Now its working! Here we go: Marchingcubes generated isosurfaces with smooth blending between given materials ( Every blending possible ...

Mirror it around, change the signs of the coords as needed, rotate the coordinate system, etc. pp.

I played around with it a bit and it seems to be not as intuitive as i thought.

I tumbled across the GLSL specifications tho and found, that GLSLs standard vertex layout expects 8 UV coords. I could encode my needed information in that one if - and here comes the part i dislike here - irrlicht ...

Oh boy, thats a big topic.

What kind of "destruction" do you want? If it is for smaller objects like boxes etc: Sure, thats quite easy. There are different approaches to that like a Box composed of smaller parts which are handles as one box until a force great enough is applied to the box. The ...