Scratch

That happens because scratch must process the wait block which includes a couple of commands to make it work.

Look what would be faster.

startofloop:

Do Something

GoTo startofloop


Or.

startofloop:

Do Something
Sleep(0)

GoTo startofloop


Just use the notes feature or broadcasts.

Hey F8Twist, what what-the says is right.

Instead of using empty blocks, use the comment feature to mark off different parts of the script. If you're not familiar with adding notes to a script, simply right click in an empty spot of the script area and you should see a pop up menu, with a choice "add comment". Then you can drag the comment onto the specific block you want. 

It's because of the way the execution engine works. If you have an extra block, that is pushed onto the stack of blocks to be executed, and since Scratch executes one block at a time from each script, that's one wasted step of the script.

coolstuff wrote:

Yes, Scratch does have a rather odd engine that's a pain to work with because the "repeat x" block not only repeats the blocks inside it but adds a painful delay of about 0.2 seconds. This means that if you want to repeat something fifty times with no delay, you have to actually repeat your blocks fifty times. It's ridiculous.

A similar, but slightly less extraneous system is used for regular blocks: approximately a 0.1 second delay is put between blocks. I just hope they improve this in future versions. 

I think that the delay was added to make movement easier. Imagine if the delay was suddenly removed - sprites would be racing around at super speed! But yes, you should use comment blocks as placeholders. They don't add lag to the script and you can write things in them!

I think it would be pointless to wait 0 seconds, on account of the fact that its just a block taking up space. 

coolstuff wrote:

Yes, Scratch does have a rather odd engine that's a pain to work with because the "repeat x" block not only repeats the blocks inside it but adds a painful delay of about 0.2 seconds. This means that if you want to repeat something fifty times with no delay, you have to actually repeat your blocks fifty times. It's ridiculous.

A similar, but slightly less extraneous system is used for regular blocks: approximately a 0.1 second delay is put between blocks. I just hope they improve this in future versions. 

Squeak is a slow language. Scratch 2.0 will be much faster (Flash executes code quickly), so that won't be much of a problem in 2.0. Remember, computers take time to execute code.

rdococ wrote:

Harakou wrote:

coolstuff wrote:

Yes, Scratch does have a rather odd engine that's a pain to work with because the "repeat x" block not only repeats the blocks inside it but adds a painful delay of about 0.2 seconds. This means that if you want to repeat something fifty times with no delay, you have to actually repeat your blocks fifty times. It's ridiculous.

A similar, but slightly less extraneous system is used for regular blocks: approximately a 0.1 second delay is put between blocks. I just hope they improve this in future versions. 

I think that the delay was added to make movement easier. Imagine if the delay was suddenly removed - sprites would be racing around at super speed! But yes, you should use comment blocks as placeholders. They don't add lag to the script and you can write things in them!

Super speed almost made me laugh. Anyway, using the repeat block without delay could:
- Crash your computer
- Crash the OS
- Freeze the browser
or
- Crash the java/flash/squeak player

Yeah, instant code execution is impossible, since ordinary matter (such as electrons) and light have a speed limit (the speed of light) of 299792458 m/s. The flowing electrons would have to be in a quantum superposition for such execution. Particles only have properties when they are observed, so to have a superposition you need to isolate the computer. And superspeed quantum computers are still experimental, so instant execution is a mere pipe dream.

Download this project. It will freak you out!

Last edited by 3sal2 (2012-07-15 15:12:50)

Apparently nobody here seems to realize why this happens.  It's not a glitch.  Scratch actually goes by frames, rather than time.  A block that says "wait zero seconds" is essentially saying "wait the shortest amount of time possible," or, "wait one frame."  I have noticed that unless you are in turbo mode, scratch typically has a maximum frame rate of 40 per second.

I know that scratch uses a "slow engine" but even something like Java can perform thousands of computations almost instantly, therefore the above ideas are false.  Also, turbo speed proves that they are false as well because it takes away that wait.

LS97 wrote:

Guys... this post dates back to more than a year...

Posting on a thread that is more than a few months old is called necroposting, and is frowned upon by the community. Please don't do this again   
Scratch on!

There, now that I've inserted my little pre-made necropost message, do we want to make a new topic on quantum physics and leave this one alone? 

Thanks for that - but if a thread is still relevant, I wouldn't call it necroposting. This is still very much an issue and the respondents actually had something to say which I think contributed to the discussion.

Also, I'd like to remind the people on this thread that mini-modding is also frowned upon by the community - please leave that kind of thing to the Community Moderators by pressing the "report" button if you have an issue.