Change Log of NGD 2.10

[PJani]

What changed since 2.09? Change log is not updated as i compared log of 2.09 and 2.10...

[Julio Jerez]

did you played the SDK?

[PJani]

Before i change from 2.09 i want to know whats differend i downloaded 2.10 but i dont know whats different.

EDIT...do i think what it is( real time destruction? ) For this feature i was waiting very long time...the only problem is how to implement this in ogre...

[Stucuk]

Before i change from 2.09 i want to know whats differend i downloaded 2.10 but i dont know whats different.

EDIT...do i think what it is( real time destruction? ) For this feature i was waiting very long time...the only problem is how to implement this in ogre...

If you download a "Diff" program (One that can tell you the difference between 2 text files) then you can see what changed in the header. The header its self didn't change alot.

[Julio Jerez]

Before i change from 2.09 i want to know whats differend i downloaded 2.10 but i dont know whats different.

EDIT...do i think what it is( real time destruction? ) For this feature i was waiting very long time...the only problem is how to implement this in ogre...

The part related to Newton should be quite trivial to implement, I cannot say in relation to Ogre,
All it needs it a way to make graphics object that csn be disabled for render until the aplication decides to turn them on.

Wait until you see the next Pawaaaa

[PJani]

Before i change from 2.09 i want to know whats differend i downloaded 2.10 but i dont know whats different.

EDIT...do i think what it is( real time destruction? ) For this feature i was waiting very long time...the only problem is how to implement this in ogre...

The art raleter to Newton should be quite trivial to implement, I cannot say in relation to Ogre,
All it needs it a way to make graphics object that cna be disampe for render until teh aplication decide to turn them on.
Wait until you see the next Pawaaaa

How bodies break? They break as predef or by complex calculations?

[Julio Jerez]

The braking is a complex calculation, but they result is a data structure that is easy and fast to use.
For real time you are limited to no more than two three or four debris pieces, but for reconstructed demolished bodies it is only limited to how fast a visual body can be enable, and how much rigid body can be created in real time.
You can easily create 20 to 30 bodies in Newton, if every thong is recalculated,
So if you Game engine support the pre created of Visual mesh that are invisible and not affect the engine performance until they are active, then it should not be a problem.
Furthermore if the graphics engine support meshes Instances, then is should be fast and low memory consumption if you reuse the shapes for equal pieces.
For example you can have a crate that is an instance that you can use it many times.
If you make the crate destructible and reuse the collision shape, then same debris geometry and Collision is use everywhere,
By tagging the debris pieces with special ID or Material the you can remove pieces from the since when the member of debris is too high and too old,
you can do that by using a Queue with, then when the Queue reach some size you just delete pieces from the top until it is back to the desire size.
That way you can have debris that are persistence as long as the count is acceptable for the engine.

This feature does not stop there; you can also make cut on geometry like Holes, carving, unions, and intersection on any mesh.

In the next version 2.11
There will be the Compound breakable that will support partial compound destruction.
For example you can have an entire building made from solid pieces, very much like the technique that Quake and Half life engine editor use,
The entire building will be converted compound collision,The engine will generate the mesh for visualization that you will convert to a mesh for your graphics engine.
Then at run time each time wall is hit or any part of the body, if the impact in larger that the max impact impulse at that point, then you get a call back.
In the call back you can querie what part will be peel off from the compound to be converted into debri, you can do that by volume queries using the impact strength for the size of the volume.
Then for each peel off piece you issue a new debris pieces just like in the prefab SDK demo.
you cann VisualMeshUpdate to and new Index list to regenerate the base mesh using the same vertex array.
Finally it will report the New Partial compound, for example say there is a tall column, and it is hit in the center,
then the pieces intersected by the hit volume will be loose debris pieces, but the top and the bottom could be two different partial compounds.
Using this you can make entire destructible buildings and even stuff like space stations that are dynamics.

How does that sound to you, you thing Ogre can deal with that?

[PJani]

Ogre can do any thing. Because of Ogre i changed from Irrlicht to Ogre in the middle of project. .

[Julio Jerez]

Ogre can do any thing. Because of Ogre i changed from Irrlicht to Ogre in the middle of project. .

That's the spirit, let us see destruction in Ogre them.

To make you salivate can you imagine the debri detail be a normal Mapped texture that show all the roughnes of the destoyed pieces.
That's right the derbri creation supports all of that you have full controll. and is is righ of Ogre capability ally.