[micapat]

I think that you can provide more functions to manage timers, because if it's just to measure execution time, there is the sawce's profiler which does it nice.

So you can add a system with more than one timer for instance. But I don't know if this module will be usefull because it exists many other ways to measure time like get_gametime( ), halflife_time( ), get_time( ) and so on...

[hleV]

Originally Posted by micapat But I don't know if this module will be usefull because it exists many other ways to measure time like get_gametime( ), halflife_time( ), get_time( ) and so on...

You can't measure function's execution time with those.

[meTaLiCroSS]

There's no Linux version yet?

[claudiuhks]

Originally Posted by meTaLiCroSS There's no Linux version yet?

I'll publish it today.

[meTaLiCroSS]

Originally Posted by claudiuhks I'll publish it today.

Will wait for it, thanks

[claudiuhks]

Linux build has been published today.

[urban_ninja]

Is it possible to add a return function for microseconds and/or nanoseconds? This module as it is is kinda useless you're plugin uses large for loops. Anything less than a loop length of 70-100 or less than 100s of functions executing at once is unmeasurable in milliseconds.

Secondly the time stamps only work when the plugins 1st load. This is useless for time stamping code buried within a condition statements that don't execute until certain criteria occurs in game play. Plugins with dynamic code where data is constantly changing on the fly need more of a real time time stamping instead of this one off at map start.

[bibu]

Originally Posted by urban_ninja Is it possible to add a return function for microseconds and/or nanoseconds? This module as it is is kinda useless you're plugin uses large for loops. Anything less than a loop length of 70-100 or less than 100s of functions executing at once is unmeasurable in milliseconds.

Since the amxx profiler doesn't work with latest builds, I wanted to try out the module finally. And I can agree with urban ninja. Because right now any other function just prints me 0.0000 . By using large arrays, it's fine though.

[Freezo Begin]

Hmm ,
how about doing something like this ?

#define MILLIS (10000)

getTime()
{
    new time0,  time1, time2,   i;
    time0 = tickcount()
    for (i = 0; i < MILLIS; i++)
    {
        server_print("%d",100)
    }
    time1 = tickcount();
    for (i = 0; i < MILLIS; i++)
    {
        server_print("100")
    }
    time2 = tickcount();
    server_print("getTime 1: %04d || getTime 2: %04d", time1 - time0, time2 - time1)
}

Well i didnt test it , i just found it ...

[claudiuhks]

This module is kinda' experimental and it has no public use...
If you want you can alter the source code and compile for yourself, I am not willing to change it anyways.

Originally Posted by bibu just prints me 0.0000 . By using large arrays, it's fine though.

AMX Mod X is fast.