NewtonTreeCollisionAddFace slow as hell

[Julio Jerez]

I do not undestand, were are you getting 2^125 so fat I know there is nothing in the visuble univese that can have a 2^128 combinatorial interation.

you are talking larger than astronomical figures. Some is wrong with that figure you are asuming that maybe each valeu in aset can interat with other value by that is never the case.

[PJani]

REMOVED text

[Julio Jerez]

I am confused, what it is that you are doing?

[PJani]

REMOVED text

[Julio Jerez]

static collsion is a base class internally, there are tree subcaless that derive form it:
collsiontree (done), higpmap (done), used collsion (not ready yet)
I will add that demo sometime today.
and I will make with a flat plane, so that is simpel and you can use it for you game.

if your data is so neetlly organized, they maybe you are right the user collsion is the best solution.
they you do not even have to make a collsion you can generated it on demand, like the highfield collision does.

[PJani]

I have seen your usermesh collision is bounded with min and max...

Code: Select all

NewtonCreateUserMeshCollision(world,vec_min,vec_max, this, &_usermeshCollideCallback, &_usermeshRayHitCallback, &_usermeshDestroyCallback, &_usermeshGetCollisionInfo, &_usermeshGetFacesInAABB, 0);


is possible to make this inf collision so i don't need to create new body(so i conserve memory and lower de/alloc calls) every time there is need for loading a chunk!? And when newton makes AABB query i would generate coresponding chunk/s and cache vertexes indexes into memory.

[Julio Jerez]

I believ you are no underthadin hwo the funtion works.
Min and Max is for passing the face that inteset the box.

wait for the flat palne demo demo so that you can use it.

[PJani]

Hmm you mean its __out or __in parameter? because i am little confused what you mean by face of box(AABB?)

[Julio Jerez]

I am going to add the user plane and use terrain, you can use those to make your game. Let me bring what I am doing to a stable point.

[PJani]

Okie, let me know when you update demos tnx!

[PJani]

Any news on usermesh?

[Julio Jerez]

the weekend

[PJani]

I have just one more question does UserMesh work or not? Because i was playing later this morning with it and it doesn't call collide callback.

[PJani]

Hmm i was thinking and would it be possible to have pointer array(each pointer pointing to one vertex) instead of index array and therefore vertex array can be removed, and data doesn't need to be stored in one vertex array, but in smaller buckets/batches. therefore there would be no need for copying together chunks of vertex arrays into one vertex array. And then i only need to update vertex pointers...atributes and face count arrays. And there is one BIG I MEAN VERY big plus i dont need to recalculate offsets for indexes, just concat precalculated vertex pointers into bigger array and send it to the engine! And that should be fast as lightning.

[Julio Jerez]

I have just one more question does UserMesh work or not? Because i was playing later this morning with it and it doesn't call collide callback.

No. that is why I could not complet the demo last week. I see if I can completed today.
The user mesh is just a subclass of the mesh collision, must the work is done it is just thet I have not converetd to be instance base.