(04-13-2010 08:32 PM)Esenthel Wrote:  you need to debug and check at which point it doesn't proceed

I cheсed it.
Trouble in this line.
Sometimes triggered, sometimes not.

Damn...
At very short distances (0-5 units). Ray not collides with player.

you can try visualizing the ray line

void Draw()
{
Renderer(..);

SetMatrix
D.line(..

see if it actually collides
you can also use callback function to test all actors in the ray test


maybe you start the ray-test from within the character shape?
maybe physx will return true only if you start ray test outside the shape.
you can try additionally testing Physics.cuts - tests if you are actually inside the shape.
(so try Physics.ray and cuts simultaneously)
I think Bloody Massacre does that when testing bullets collisions

I vizualized ray in game.cpp (I write code based on Bloody Massacre). Start of line - center of AI-actor, end - center of Player-actor. Point of collision drawing on surface of Player-actor. Screen


But main ray-testing code uses in AI.cpp in update(). Maybe it's problem?

P.S. It very strange... Today this code one time worked on small distance too.

I solved the problem. When I replaced pos() on T.pos() all works perfectly...

How to exclude Character from SSAO-effect?

AO works for fullscreen, can't exclude objects from it

Mmm... What about precalculating AO for terrain + embed into terrain objects? Is this possible now?

only additional AO for terrain is calculated (and stored per vertex as vertex color) that is not however the SSAO post-process effect (only terrain vertex color)