Does anyone (aka nXIII) know where to change the step time in Scratch? I just want to make a super turbo mode, because I have projects that would really need it.
Offline
henley wrote:
I'm sorry, if you want your projects to be fast, and not lag, then don't use Scratch.
I know that. But I also know that they purposely made the step time low. I want to know how to make it really fast.
Offline
henley wrote:
I'm sorry, if you want your projects to be fast, and not lag, then don't use Scratch.
You could put it in like 150 times, then it be much more faster than repeat 150
Offline
recycle49 wrote:
henley wrote:
I'm sorry, if you want your projects to be fast, and not lag, then don't use Scratch.
You could put it in like 150 times, then it be much more faster than repeat 150
Except that I have something that repeats 44000 times.
Offline
ScratchReallyROCKS wrote:
recycle49 wrote:
henley wrote:
I'm sorry, if you want your projects to be fast, and not lag, then don't use Scratch.
You could put it in like 150 times, then it be much more faster than repeat 150
Except that I have something that repeats 44000 times.
Thats a big number
IT'S OVAR 9000
Offline
soupoftomato wrote:
ScratchReallyROCKS wrote:
recycle49 wrote:
You could put it in like 150 times, then it be much more faster than repeat 150Except that I have something that repeats 44000 times.
Thats a big number
IT'S OVAR 9000
Yeah. I'm making a virtual computer with 44000 bytes of memory. That's about 44 kilobytes!
Offline
nXIII wrote:
Well, the problem now is that the execution engine isn't fast enough. If you want a faster Scratch in Turbo Speed, you have to rewrite the execution engine.
Okay, never mind then.
Offline
ScratchReallyROCKS wrote:
they purposely made the step time low.
WHAT!? O_o
Offline
Jonathanpb wrote:
ScratchReallyROCKS wrote:
they purposely made the step time low.
WHAT!? O_o
Believe me, once I started using languages with a high step time, it got a LOT harder.
Offline
ScratchReallyROCKS wrote:
recycle49 wrote:
henley wrote:
I'm sorry, if you want your projects to be fast, and not lag, then don't use Scratch.
You could put it in like 150 times, then it be much more faster than repeat 150
Except that I have something that repeats 44000 times.
You could have it ten times and repeat 4400.
Offline
oh. by the way, the step time is actually set to fastest in turbo speed (one action every 0 ms). The repeat loops have a 40 ms delay, you could change that to make it 1760000 times faster (i think). that still gives about 1ms per block execution + 44000 repeats (1 ms), which makes a total of 88 thousand ms per run.
That means the best you can get (in theory on a really fast PC) is 88 seconds per run!
EDIT
@coolstuff: you made it simple, but we said the same thing
Last edited by LS97 (2010-10-12 07:43:22)
Offline
Let me explain how 'turbo speed' works versus normal Scratch speed (just to clarify things for people who haven't looked at the Scratch source):
Normal mode runs ALL the processes until they give up control (yield), then waits until the next frame (a set time).
Turbo speed runs processes CONTINUOUSLY until "time is up"--the frame time has run out. Then it redraws (once!) and does the same thing again.
Offline
nXIII wrote:
Let me explain how 'turbo speed' works versus normal Scratch speed (just to clarify things for people who haven't looked at the Scratch source):
Normal mode runs ALL the processes until they give up control (yield), then waits until the next frame (a set time).
Turbo speed runs processes CONTINUOUSLY until "time is up"--the frame time has run out. Then it redraws (once!) and does the same thing again.
Yeah, I pretty much figured that much out myself by comparing how scripts run in the two modes.
Offline
You could compile the blocks directly into smalltalk.
Offline
TheSuccessor wrote:
You could compile the blocks directly into smalltalk.
Yea, at one point that was what I was doing with Blocks++.
But now Blocks++ either doesn't exist or is the same thing as JScratch, which in turn is the same thing as Panther 2.0.
Offline