I've been trying to make an animation but I have to wait between the times and audio so I suggest a project speed multiplier. This is kinda like turbo mode but better.
Let's say your script is this:

when green flag clicked
play sound [s v]
wait (8) secs
next costume
wait (8) secs
next costume

With the option on, your whole project would be 2 times as fast (maybe an option for 4x, 8x so on). The sounds would be 2x fast and the wait blocks would be two times as fast. The timer sensing variable would be twice as fast too. Time or Date blocks wouldn't change, because this is more for animations and that would mess up fixed time. If you turn this setting on, you would be cut off from cloud so you can't cheat on a game.

So the project above would equal this in 2x mode, but it won't change code, this is just a visualization of the speed multiplying:

when green flag clicked
play sound [s2x v]
wait (4) secs
next costume
wait (4) secs
next costume

This could be toggled with a slider at the top of the code editor or on the project page. On the project page, you'll need to use Ctrl+Shift. Long animations could be made faster and easier without having to wait for the wait block. To clarify, this is not a block. It is a setting.
Mockup


if this is kinda too explained, know i made this when i started foruming

I agree, I always deal with waiting. I was making a version of life is fun but with my animation, later it took sooooooooooooo long i quit.















E

scoobis123 wrote:

I agree, I always deal with waiting. I was making a version of life is fun but with my animation, later it took sooooooooooooo long i quit.















E

That always happens. That's why I never make animations.

When making animations, you could separate your animation into short parts that can be started with a broadcast so that you can start in the middle of a section by sending a broadcast. Each section could then autocontinue to the next by calling the next broadcast

This would be a cool feature but what about the times when scratch cannot run at that speed due to processing power? How would that work?

--Explosion-- wrote:

This would be a cool feature but what about the times when scratch cannot run at that speed due to processing power? How would that work?

It not going to be like turbo mode, it is just gonna be 2x speed. The sound and wait blocks will just go faster. IDK what will happen with a lot of frames.

--Explosion-- wrote:

This would be a cool feature but what about the times when scratch cannot run at that speed due to processing power? How would that work?

I'm assuming it's not a perfect 2x speed and can be slowed down by lag (kind of like what happens at normal speed)

bump

bump

Isn't this is what Turbo Mode is for?

BestUsernameSoFar wrote:

Isn't this is what Turbo Mode is for?

Turbo mode doesn't make timers or music faster.

What would happen to the datetime blocks and days since 2000?

NxNmultiply wrote:

What would happen to the datetime blocks and days since 2000?

Well, I think they should stay the same because this is more for animations.

Interesting…so it's like fast motion? This could be useful if you want to skip ahead to a certain point in an animation without having to watch through it again. Support!

bump

Semi-Support, since this could be more useful than turbo mode. However, I have a question. Would this feature be a block like

set project speed to[x2 v] ::sensing

or another shortcut (like turbo mode is shift-click the flag)? I can't really say whether this would be useful or not yet.

AlexeyChub wrote:

Semi-Support, since this could be more useful than turbo mode. However, I have a question. Would this feature be a block like

set project speed to[x2 v] ::sensing

or another shortcut (like turbo mode is shift-click the flag)? I can't really say whether this would be useful or not yet.

It would be a setting like turbo mode.

bump

bump