Sign in to follow this  
Medo Mex

Efficient Way To Detect Vision

Recommended Posts

Adam_42    3629

Here's some ideas:

 

1. First check to see if the player is within the cone of vision from the enemy (i.e. is the player close enough and in front). If not then there's no need for a ray cast.

 

2. All ray casts should probably start from the enemies eye. It's the target on the player that's harder to choose.

 

3. To minimize the number of ray casts one option is to remember what happened last time you did a ray cast. If the ray cast hit the player then repeat a ray cast to the same target next time. If not then cycle through targets like head, hands, feet, torso, weapon, etc. A few frames of latency for detection of a partly obscured target shouldn't be an issue, you'll probably want to add some artificial latency anyway to simulate the reaction time of a human.

 

4. You may want to let enemies that are actively attacking the player do more ray casts than others.

Share this post


Link to post
Share on other sites
Postie    1559

[quote name='Adam_42' timestamp='1358377107' post='5022334']
2. All ray casts should probably start from the enemies eye. It's the target on the player that's harder to choose.
[/quote]

 

I remember reading a post from the Wolfire guys, and they solved this by picking a different random point on the player's mesh every time the test is performed.

Share this post


Link to post
Share on other sites
Medo Mex    891

Hi Adam,

 

Can I create a cone shape starting from the enemy eyes to detect collision and once the collision is detected I do raycasting from the enemy eyes towards the player to check if the enemy got direct sight on the player?

Share this post


Link to post
Share on other sites
Aqua Costa    3691
Can I create a cone shape starting from the enemy eyes to detect collision and once the collision is detected I do raycasting from the enemy eyes towards the player to check if the enemy got direct sight on the player?

Simple math can probably be enough to do the vision cone check.
 

int fastVisibilityCheck(float4 playerPos, float4 enemyPos, float4 enemyLookDir,
                        float maxViewDistance, float cosHalfMaxAngle)
{
     //Vector from enemyPos to playerPos
     float4 view = playerPos-enemyPos;
     float distance = sqrt(view.x^2 + view.y^2 + view.z^2);

     if(distance > maxViewDistance)
          return 0; //not visible

     view = normalize(view);
    
     //cosine of the angle between the view vector and the direction the enemy is looking
     float cosAngle = enemyLookDir dot view;

     //check if player is inside the cone
     if(cosAngle < cosMaxAngle)
          return 0; //not visible

     return 1; //visible
}

 

Use the previous function like this:

for(int i = 0; i < enemies.size(); i++)
{
     if(fastVisibilityCheck(player.pos, enemies[i].pos, enemies[i].lookDir, enemies[i].maxViewD, cos(enemies[i].fieldOfView/2)))
     {
          //use raycasting to check if enemy can really see the player
     }
}

 

 

Edited by TiagoCosta

Share this post


Link to post
Share on other sites
Medo Mex    891

@TiagoCosta: Need a little bit of more clarification.

 

playerPos is the beginning of the cone (enemy eyes position)? Is that true?

someNumber is how far the enemy can see.

someOtherNumber: How do I get this value?

Share this post


Link to post
Share on other sites
Aqua Costa    3691
@TiagoCosta: Need a little bit of more clarification.

playerPos is the beginning of the cone (enemy eyes position)? Is that true?
someNumber is how far the enemy can see.
someOtherNumber: How do I get this value?
Sorry I didn't had time to comment the code before.

I updated the code in my last post... should be easier to understand. Edited by TiagoCosta

Share this post


Link to post
Share on other sites
Medo Mex    891

How do I calculate enemyLookDir  from the rotation? I mean the enemy look direction depends on its own rotation.

 

Another thing is: Does this work well without performance issues? I have to iterate through all the models to check for vision on every one, in performance manner, is that way better or using a cone shape and detecting collision?

 

Enemy1 -> iterate through all the models every frame to detect vision

Enemy2 -> iterate through all the models every frame to detect vision

Enemy3 -> iterate through all the models every frame to detect vision

......

Enemy100 -> iterate through all the models every frame to detect vision

Etc...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this