Timer Query

[Ayanami]

I'm figuring out which Timer System would be good for both high and low frequencies. Or would I have to use separate timers for High and Low frequencies?

 

[Dirac]

Anything that isn't periodic deserves the new version of TimerUtilsEx, otherwise go T32.

You can also experiment with Nestharus's timer systems which are faster, but they're a bit more complicated.
Constant Timer Loop
Timer Tools

 

[Nestharus]

The Timer Tools post provides details on when to use which thing ; )

Constant Light Timer Queue 1 Demo
Use when dealing with constant timeout 1 shot timers with constant methods of timeouts that are 2+. Usually used for expiring effects. Essentially use this when there is a low chance for merges between timers (perhaps highly infrequent timers).

Constant Timer Queue Demo
Use when dealing with constant repeating timeouts.

Constant Timer Method Demo
Use when dealing with repeating timers of an unknown timeout with a constant method

In cases where the method is completely unknown, use regular timer data attachment. 1 Shot timers can run through Constant Timer Queues/Consant Timer Methods if there are many one shot timers of the same timeouts, otherwise the overhead on creation/destruction isn't worth it.

Light Timer Queue 1 will always be worth it for 1 shot timers when Constant Timer Queue isn't (perhaps infrequent timers, high period, essentially low chance of merge).

For timers that run 32x a second, Constant Timer Loop is the best option.


If you are in it for the simplest options rather than the best performing options, then use T32 and vex's TimerUtils ; ).

 

[Bribe]

That's a shocker, you of all people supporting Vex's TimerUtils over the rewrite Magtheridon and I made.

Interesting that you haven't even commented on said resource. Would love to know what you think about it as Vexorian has commented on it.

 

[Romek]

T32 for high frequency stuff, TimerUtils (whichever version) for low frequency stuff.

That's all you need. They perform extremely well, and are also very easy to use.

 

[Dirac]

That's a shocker, you of all people supporting Vex's TimerUtils over the rewrite Magtheridon and I made.

Interesting that you haven't even commented on said resource. Would love to know what you think about it as Vexorian has commented on it.

Bribe please read my post again :S

 

[dudeim]

Bribe please read my post again :S

I think he was talking to Nestharus.

 

[Nestharus]

That's a shocker, you of all people supporting Vex's TimerUtils over the rewrite Magtheridon and I made.

Interesting that you haven't even commented on said resource. Would love to know what you think about it as Vexorian has commented on it.

Eh, vex's or urs, doesn't really matter too much.



If you want maximum performance, use the ones I wrote. If you want more ease of use, use vex's/mag's and T32. End of story ^_^.

 

[tooltiperror]

> End of story ^_^.
noe.jpg

Timer systems are subjective. If you use just TimerUtils, unless you have a very operation intense map, you will be completely fine. The slim chance that you need something more powerful, T32 will work.

 

[Nestharus]

Timer systems are subjective. If you use just TimerUtils, unless you have a very operation intense map, you will be completely fine. The slim chance that you need something more powerful, T32 will work.

Hence why I said if you want ease of use, use TimerUtils/T32. If you want maximum performance, use those other libs, lol ; P. And keep in mind that the max performance will only show in maps in cases where some serious operations are going down, like a projectile system.

Also, the increase performance does come at the cost of an increase in code and complexity.