For real time applications, the delay introduced in non-Turbo mode is really a problem. I'm aware of Atomic Procedures, but that's a different issue, I still want multi-tasking, but I want to control the timing myself.

Here's an example project: 3D BallShootArcade that runs fine in Turbo mode but is unplayable otherwise. I believe the problem is the loops in the main loop needed for Z-sorted drawing and more loops for hit testing.

EDIT:

I changed to code a bit to just have one forever loop that controls all the other Sprites via messages and it's now playable in non-Turbo mode, but Turbo mode is still much smoother running.

Support.
They should be blocks, enable turbo mode and disable turbo mode.

Support

Totally support this.

Splodgey wrote:

Support.
They should be blocks, enable turbo mode and disable turbo mode.

I don't understand why you would want this.

Why would you want turbo mode to be disabled for part of a project? The only point to Turbo mode as I understand it is to slow down loops so they don't run essentially instantaneously. If you're controlling the timing of the project, I'd think you'd want everything to run as fast as possible with any pauses in the code just done by wait blocks.

Ralph

RDoc wrote:

Splodgey wrote:

Support.
They should be blocks, enable turbo mode and disable turbo mode.

I don't understand why you would want this.

Why would you want turbo mode to be disabled for part of a project? The only point to Turbo mode as I understand it is to slow down loops so they don't run essentially instantaneously. If you're controlling the timing of the project, I'd think you'd want everything to run as fast as possible with any pauses in the code just done by wait blocks.

Ralph

I have come across times where I would want it disabled for part of it, but I can't remember what it was. Plus, this was back in 1.4, before you had the “run without screen refresh” option.

I think I've found a duplicate:

http://scratch.mit.edu/discuss/topic/2603/

It's pretty old, from back in February. But you may as well bump that one up instead.

mathfreak231 wrote:

I think I've found a duplicate:

http://scratch.mit.edu/discuss/topic/2603/

It's pretty old, from back in February. But you may as well bump that one up instead.

Also, this, this, and this.

mitchboy wrote:

mathfreak231 wrote:

I think I've found a duplicate:

http://scratch.mit.edu/discuss/topic/2603/

It's pretty old, from back in February. But you may as well bump that one up instead.

Also, this, this, and this.

This topic was about setting it as an ATTRIBUTE, not using blocks to turn it on+off. The third topic you listed there isn't even about blocks that turn turbo mode on and off, it was more of a new option like “run without screen refresh”.

Ah well, if there's been that much discussion for so long, it sounds like it's not going to happen.