Ability to speed up or slow down scripts or sprites

megaman100

It would be nice if we could speed up and slow down scripts in sprites.

set speed of [script 1 v] in [myself v] to [2x v]:: control

set speed of [script 1 v] in [myself v] to [50% v]:: control

If you want to know more about adding names to scripts check out my proposal about adding names to scripts here.

Last edited by megaman100 (Aug. 24, 2018 20:40:44)

LuckyLucky7

You could use turbo mode for speeding up scripts, Scratch runs scripts normally by default, but support for slowing down scripts. Slowing them down can be useful for debugging and finding errors in scripts.

ZappyBarbecue10

megaman100 wrote:
It would be nice if we could speed up and slow down scripts in sprites.
set speed of [script 1 v] in [myself v] to [2x v]:: control

set speed of [script 1 v] in [myself v] to [50% v]:: control
If you want to know more about adding names to scripts check out my proposal about adding names to scripts here.

It would be cooler to make it more specific and go with something like this:

set screen refresh speed of [script 1 v] in [myself v] to [30 v] fps:: control

set screen refresh speed of [script 1 v] in [myself v] to [60 v] fps:: control

Or at least something similar. It would help in a lot of projects

Locomule

That would be awesome! Here is one of my favorite debugging tools..

wait until <key [space] pressed?>
wait until <not <key [ space] pressed?>>

I stick those in anywhere I precisely need the project to fully pause (not stop) so I can check variables, sprite positions, etc and find out what is going wrong. These blocks are so handy I always keep a set in my backpack just for debugging.

Last edited by Locomule (Jan. 10, 2019 17:54:01)

cannonball84

why don u just use this?

wait ((31) / (FPS)) secs

ResExsention

cannonball84 wrote:
why don u just use this?
wait ((31) / (FPS)) secs

(FPS)

is not a variable.

Botcho_Otkho

ResExsention wrote:
cannonball84 wrote:
why don u just use this?
wait ((31) / (FPS)) secs
(FPS)
is not a variable.

Exactly. And also, in normal mode (not in Turbo), the scripts take * time to run, so putting a Wait script just adds more time between scripts, it doesn't slow them down.

ZeroFury

megaman100 wrote:
It would be nice if we could speed up and slow down scripts in sprites.
set speed of [script 1 v] in [myself v] to [2x v]:: control

set speed of [script 1 v] in [myself v] to [50% v]:: control
If you want to know more about adding names to scripts check out my proposal about adding names to scripts here.

that would be very good

dhuls

This feature is in Scratch Jr but (1 Scratch Jr is for Android and iPad (2 It's made for kids ages 5-7 (3 it's missing variables and (4 the speed up/slow down feature is per sprite. Although you could still use Turbo Mode it breaks scripts (some projects are programmed to stop
when turbo mode is activated) Support, also these blocks could work

Set speed to ()
Slow down by ()
Speed up by ()

They would be in the Control category
note 1: the latter 2 can be replaced with:

Change speed by ()

note 2: nothing in this post is meant to insult Scratch Jr

p-p-p-p-p-p-p-p-p-p-

no support. You can work around it like this:

when green flag clicked
say [Hello!] for (foo) secs
wait (foo) secs

And then keep on adding waits or other times on it. Then, on the other sprite this can work:

when [ space] key pressed
set [ foo] to [5]

etc.
This is a harder way though

Last edited by p-p-p-p-p-p-p-p-p-p- (Oct. 8, 2020 12:34:09)

rontinn

megaman100 wrote:

set speed of [script 1 v] in [myself v] to [2x v]:: control

You should probably only have the ability to slow down scripts, not speed them up

Last edited by rontinn (Nov. 23, 2020 01:44:21)

lm1996

If you want to slow them down, use wait blocks.

when this sprite clicked
glide (4) secs to x: (-63) y: (-49)
vs.
glide (8) secs to x: (-63) y: (-49)

when green flag clicked
go to [random position or else v]
go to [random position or else v]
vs.
go to [random position or else v]
wait (0 v) secs
go to [random position or else v]

Also waiting 0 seconds is a real thing.

chrdagos

support.

it can be of much use for debugging a script. and even though there is a workaround, it would be a pain to use.
although it would make more sense if it was a c-block

GoogleInScratch

lm1996 wrote:

If you want to slow them down, use wait blocks.

when this sprite clicked
glide (4) secs to x: (-63) y: (-49)
vs.
glide (8) secs to x: (-63) y: (-49)

when green flag clicked
go to [random position or else v]
go to [random position or else v]
vs.
go to [random position or else v]
wait (0 v) secs
go to [random position or else v]

Also waiting 0 seconds is a real thing.

What does the vs. block do

Lerconn_Games

GoogleInScratch wrote:
lm1996 wrote:
If you want to slow them down, use wait blocks.
What does the vs. block do
It's too late, but I think it's just a filler block they used to indicate “whatever blocks are there”, similar to:
... :: grey stack

Renzy_11

WHAT ABOUT timers?

Discuss Scratch