Which of these if the fastest

I'd like to know what is the fastest method of going through a number of structs/any other things, with regards to timers

A - Looping through a series of (whatevers) on a single timer i.e.

B1 - Attaching the data to separate timers using HSAS
B2 - Attaching the data to the same timer using HSAS (if that's possible)

C1 - Same as B1, using HAIL
C2 - Same as B2, using HAIL (again, is it possible?)

D1 - Same as B1, using ABC
D2 - Same as B2, using ABC (,again is it possible?)

E - Timer Ticker

F1 - B1 using gamecache
F2 - B2 using gamecache (again, is it possible?)

G - Any other attachment systems involving timers :P

Toadcop?

A is by far the fastest

Simpler = Faster.

Always. Unless, of course, you have grotesquely bottlenecked hardware...

A is the fastest, possibly followed by E.

Thanks for that :)

@Dark.Revenant: Not 100% sure on what you're saying

unless you have fucked up computer hardware

I was talking about the simpler = faster bit :P Faster in what way? In coding the stuff, or in how fast the code works when it is actually used?

10 year old PC

If you can make the thing with a single timer, then A (without the array) would be best performance (since you wouldn't need attaching).


If you need multiple timers, you need to attach. HSAS/CSData is fastest.

If you had really a lot of objects used by the same timer, like 750 or 1000, A would give you a very high fps, the problem is that it is not preemptive , so regardless of the high fps the players will feel like it periodically freezes. Something with attaching will in that case really make the game slower, but the players would actually feel better playing it since at least the game speed is consistent.

@Vexorian: But what if the number of objects is much lower... in the region of <= 100 (that'd be an absolute maximum IMO). Would the periodic freezing be noticeable, or would that vary depending on the player's PC?

@Themerion: I know how to do the loop :)

Hmmm, isn't HAIL as fast as HSAS? I remember someone telling me that there was little/no speed difference between the two :P

Anyway, if multiple timers aren't as fast as a single timer, I will just stick to a single timer

I got in that situation a lot of times and it wasn't noticeable.

So, if I was looping through 10 slide instances at any one time, a single timer with a loop would be the best way to go?

Or would this be one of those 'do whatever you think is best' kinda things, where the differences are minimal?

Yeah, HAIL is approximately equal to HSAS. CSData will probably be more common to use though (since it comes bundled with the Caster System).


For attaching to units, I think PUI is superior.


Yup.


Yup.