NewtonTreeCollisionGetVertexListIndexListInAABB is commented

[pHySiQuE]

NewtonTreeCollisionGetVertexListIndexListInAABB is commented out in Newton.h at line 747, although the function is in the CPP file.

[Julio Jerez]

I need to modify it after the chnge to collsion intsance and I never did. are you using that function?

[pHySiQuE]

We're not actually using it yet, but we will use it when I add projected shadows. We use this to quickly extract a surface from a big chunk of BSP geometry. So maybe we'll need it in about four weeks.

[belfegor]

I also need this function for decals.

[Julio Jerez]

Ok I will renable it.

[belfegor]

Bump. It is still disabled.

I hope you are well and in a good health?

[Julio Jerez]

I know, I had to complete the refactoring of the material and contact first.
Now I will re enable that function

[Julio Jerez]

Ok thsi funtion is back on, teh name now is: NewtonTreeCollisionGetVertexListTriangleListInAABB

[belfegor]

Thank you for update.
Now to wait for player controller changes too.

EDIT: Just tried this function. How can vertexCount be so high comapared to tri count returned? i expected to be something like 3 * triCnt.



Unless it returns total vertex count in collision shape?

[Julio Jerez]

The vertse count is the total vertex in the collsion tree, teh funtion does no make a copy of the vertices if juist pass the pointe and the veretx count,
teh only thong is does is tha if find teh indice to the face intersecting teh AABB and copy the to the index array passed by teh function.

think of D3D making a huge veretx array and only rendering some face out of that array.

[belfegor]

I have more stupid question.
What do you think, is it better to use this function for gathering face attributes for player feet or to do that in material callback, when you finish player controller?
Is it expensive to call it every frame compared to same thing in material callback, consider that will be called also for multiple AI agents as well ?

Thank you for your time.

[Julio Jerez]

Locig say the traping the id durin teh call back wousl save time.

however software develeopeen is crazy, each tiem I make prediction liek that, I come out wrong.
I would try both see whi si better. I can certann;ly see that NewtonTreeCollisionGetVertexListIndexListInAABB can be more flexible, but if I have to guess I say teh callback is more efficient