Scratch

Almost not faster at all.

I measured my Very Large Factorials program calculating 1000!. The results:
Normal: 9.800
Turbo mode (flash): 9.783

And the result was probably me being slow with the timer (I used online stopwatch).

Conclusion: Turbo mode is not faster.

BirdByte wrote:

Molybdenum wrote:

Almost not faster at all.

I measured my Very Large Factorials program calculating 1000!. The results:
Normal: 9.800
Turbo mode (flash): 9.783

And the result was probably me being slow with the timer (I used online stopwatch).

Conclusion: Turbo mode is not faster.

That does, however, depend on the project.

Turbo mode basically does single-frame on repeat blocks, breaking in every now and then. Wait times are cut in half.

Yeah. It seems that most sprite related things (simple games, art (pixel sprites that go over the whole screen, raycasters) are faster with turbo, but list related things can range from no effect (VLF), from being a lot faster (GIbberish generators).

Last edited by Molybdenum (2012-08-09 09:05:02)

BirdByte wrote:

Molybdenum wrote:

BirdByte wrote:

That does, however, depend on the project.

Turbo mode basically does single-frame on repeat blocks, breaking in every now and then. Wait times are cut in half.

Yeah. It seems that most sprite related things (simple games, art (pixel sprites that go over the whole screen, raycasters) are faster with turbo, but list related things can range from no effect (VLF), from being a lot faster (GIbberish generators).

I guess the math functions delay Turbo mode.

Could be.

It's much faster when you need it. See the third project on my page for proof. I can't say exactly how much faster it is. I do know that it's much faster online than offline.

Also, if you see my project, you'll see that turbo mode has practically no effect at all on the wait () secs block (used at the intro to the project).

Last edited by PhirripSyrrip (2012-08-09 16:40:56)