Murdoc Loch - Total Noob | Forums

[GAS_PR1CES]

that gif. should be a RLP.

best gif ever.

[dasraizer]

that gif. should be a RLP.

best gif ever.

+1


made a google doc for 2 dimensional array, this is only an outline but combined with looping should give you some idea the power of vectors. Atomized was all done with vector arrays ,loops ,get/set and filters with 10xOPE/Hidden for the atom drawing, 1 bit of code handled all 10 atoms AI and the OPE/Hidden drawing (based on switch result that compared the atom index against the item case for drawing) then the index was incremented tested and looped back for the next atom to be handled if required, all this took place in just over a tick

[nannerdw]

*make a loop
interval trigger(disable after 1 tick)->do some stuff->increment index->filter test index less 81->
true->back to do some stuff, false-> either state enable the interval or state enable say button movement that then on select enables the loop interval.
the good thing with doing this is the game will easily handle 81 iterations if your logic code in it is fairly short, if not just break out of the code periodically by state enabling the interval, could do this with modulo index and test=0

I like that. I'll probably start doing most of my large loops like that, so a single, long chain won't cause my impulses to get dropped. It happens a lot when I'm trying to loop through visibility events, because they take so long to execute.

[dasraizer]

in a nut shell yeah, as long as the code in the loop is not mega complex or really long , if it does kill the impulse, just break the loop and enable the interval again, ok it does add another tick to the cycle each breakout but still much faster than looping with an interval timer, not really had too much problem with visible event, but i've not really done much more than turn a single item of in each pass.