[pirvu]

PHP Code:

if (ducking[ent])

{

for (new i=0;i<8;i++)

{

xs_vec_add(vec_points_crouching[i], origin, end)

if (is_point_visible(start, end, host))
return FMRES_IGNORED

}


for (i=8;i<16;i++)

{
xs_vec_mul_scalar(vec_points_crouching[i-8], 0.5, addict)
xs_vec_add(addict, origin, end)

if (is_point_visible(start, end, host))
return FMRES_IGNORED
}

}  

else
{
for (new i=0;i<8;i++)
{

xs_vec_add(vec_points_standing[i], origin, end)
if (is_point_visible(start, end, host))
return FMRES_IGNORED
}


for (i=8;i<16;i++)

{
xs_vec_mul_scalar(vec_points_standing[i-8], 0.5, addict)
xs_vec_add(addict, origin, end)
if (is_point_visible(start, end, host))
return FMRES_IGNORED
}

} 


I am a C++ scripter so first i dind't read xs_vec_add ,etc ;)

Also , good job ;)

[h010c]

Test with real players was not very optimistic.
24 players of 32 - ping raised from 20 to 80, from 50 to 150

But I must say that my server has some other "heavy" plugins. CSDM + itemmod + sentryguns + lasermines + monstermod + something else, and all are slightly modified to be more "heavy". Probably a default installation of amxmodx with this plugin would run fine.

[ot_207]

Originally Posted by h010c Test with real players was not very optimistic. 24 players of 32 - ping raised from 20 to 80, from 50 to 150 But I must say that my server has some other "heavy" plugins. CSDM + itemmod + sentryguns + lasermines + monstermod + something else, and all are slightly modified to be more "heavy". Probably a default installation of amxmodx with this plugin would run fine.

I am not surprised by this result.
I will try to improve the newer versions to work on less point checks.
Anyway the plugins that you have posted above are trully heavy. You really have a big server (as plugins I must say). You need a lot of CPU/memory to handle such a biggie.

Thanks for testing it!

[SchlumPF*]

ive never seen a c++ programmer who didnt indent his code :O

[pirvu]

Originally Posted by SchlumPF* ive never seen a c++ programmer who didnt indent his code :O

First of all i didn't look at that function so well
Second i was in a hurry
Third .. i often see that you Amxx Scripters don't try to optimize codes cuz you don't care about execution time ,etc

And i posted another one ... he didn't look at it ..

Also .. From 8 points can it be made to 4 ?

Like the parallelepiped ABCDEFGH.. to check just BDEG first diagonal up and second down
Cuz it's less probably to see Point A and not B or D or E

Just an idea ;)

[ot_207]

Originally Posted by pirvu First of all i didn't look at that function so well Second i was in a hurry Third .. i often see that you Amxx Scripters don't try to optimize codes cuz you don't care about execution time ,etc And i posted another one ... he didn't look at it .. Also .. From 8 points can it be made to 4 ? Like the parallelepiped ABCDEFGH.. to check just BDEG first diagonal up and second down Cuz it's less probably to see Point A and not B or D or E Just an idea ;)

The code you edited above, still not a good suggestion.

[Pamaliska]

That is what the plugin is suposed to do when we talk about wallhacks.

You don't get it. Players disapper before they reach a cover. If that is what you want it to do, then fine. I think it is an unintended feature

[h010c]

Originally Posted by Pamaliska You don't get it. Players disapper before they reach a cover.

http://www.youtube.com/watch?v=r3gvnQ7qenY
May be this is your problem ?

[Pamaliska]

Not it's not, because it's a default cvar value. I've noticed other players have the same problem when I was spectating them.

[turshija]

Can you check if player is moving forward or backward or strafing left - right ?
because you can optimize code by checking only half of the points ...

Dunno if it could work, but something like this (ill try to explain lol):



lets say this is player when we look from the top ...
(i've put only 4 points to make this simpler)

so here are few possible thigs:

lets say player is moving forward:
if player is visible, then we can just check for point 3 and 4, and when these 2 points become invisible, player went behind the wall ...
if player is not visible, then keep checking for points 1 and 2 until they become visible ... if they do, player just ran into our sight ...

and then you can separate that into 4 categories:
-player moving forward
-player moving backwards
-player strafing left
-player strafing right

for each category you check different points ...

I have no idea if anyone can understand what I wrote (lol) and I have no idea if that could work better than current calculations, but maybe it should work coz you are checking less points ...