When you import animations into scratch or make one on scratch, you probably want it at a specific frame rate, but how scratch is now you have to guess a lot of just say it’s good enough when it’s either too slow or too fast. Adding an FPS block would be helpful in making animations better and easier to make on scratch, and pretty helpful to animators here.
How it works:
It’s pretty self explanatory, but it makes your costumes go at a specific frame rate. So if the frame rate is at 1, it would wait 1 second to go to the next costume. If it were 30, it would change 30 costumes in 1 second, this would be the maximum.
Workarounds:
You could make an FPS counter and use that, but it’s not reliable and doesn’t work properly
Importing at a specific frame rate doesn’t work either, because the frames change when you put it into scratch as the 1 or 2 ‘pictures’ they are.
Another but more complicated workaround is this:

Credits to @-Valtran- for making it
This works better and doesn’t lag, but I didn’t see a big difference with it than with the seconds block; and it’s very complicated
————————————————
Pros and cons
Pros:
.It’s easier to animate
.You can make things closer to exact
.it’s easy to use
Cons:
.might be hard to implant
.guessing might be good enough
.the majority of people here make games instead of animating
————————————————
Conclusion
This would help animators a lot and make things easier, more exact, and less frustrating. It might also be hard to implant and not get used by the majority of the community.
—————————————————————————
Edits
-better explanation
-more workarounds
I just realized I should have said “an” fps block

I know there’s a duplicate, I know the name of the og topic, but I can’t find it.
But support, it would help meme makers with making their memes fpsi

-OdysseyCentral- wrote:

(#2)
I know there’s a duplicate, I know the name of the og topic, but I can’t find it.
But support, it would help meme makers with making their memes fpsi

This?: https://scratch.mit.edu/discuss/topic/221542/

Knightbot63 wrote:

-OdysseyCentral- wrote:

(#2)
I know there’s a duplicate, I know the name of the og topic, but I can’t find it.
But support, it would help meme makers with making their memes fpsi

This?: https://scratch.mit.edu/discuss/topic/221542/

Not this, I remember there being a slightly older (or newer) topic on FPS blocks.

-OdysseyCentral- wrote:

Knightbot63 wrote:

-OdysseyCentral- wrote:

(#2)
I know there’s a duplicate, I know the name of the og topic, but I can’t find it.
But support, it would help meme makers with making their memes fpsi

This?: https://scratch.mit.edu/discuss/topic/221542/

Not this, I remember there being a slightly older (or newer) topic on FPS blocks.

I saw a topic before this about a built in fps counter if you’re talking about that, but if you are then this isn’t a duplicate
This was it: https://scratch.mit.edu/discuss/topic/309481/?page=1#post-3202935
I think you mean this: https://scratch.mit.edu/discuss/topic/221542/

Bump

Bump

A few workarounds:

Here's a standard method.

repeat ()
next costume
wait ((1) / (Desired FPS)) secs
end

Here's a slightly more complicated workaround, but it's reliable and even better isn't affected by lag.

-OdysseyCentral- wrote:

it would help meme makers with making their memes fpsi

Not really. This is for costumes. I am unaware of how it would affect motion blocks, but I don't think it would help a lot in that manner. A better method would be FPSI easing or cached tweening anyway.

-Valtren- wrote:

A few workarounds:

Here's a standard method.

repeat ()
next costume
wait ((1) / (Desired FPS)) secs
end

Here's a slightly more complicated workaround, but it's reliable and even better isn't affected by lag.

-OdysseyCentral- wrote:

it would help meme makers with making their memes fpsi

Not really. This is for costumes. I am unaware of how it would affect motion blocks, but I don't think it would help a lot in that manner. A better method would be FPSI easing or cached tweening anyway.

Ty, but what goes in the space after the +?

(() + (0))

Depending on how well it works, I might close this, possibly

Dogs-are-amazing1 wrote:

Ty, but what goes in the space after the +?

(() + (0))

Depending on how well it works, I might close this, possibly

that's the costume offset. Say you wanted to animate from costume 50 to costume 80, you would code the below:

reset pro gamer timer :: custom
repeat until <[79] <(costume [number v] :: looks)>
switch costume to (((Pro gamer timer) * (30)) + (50))
end

This would switch the costume until costume 80, and do so in an FPSI manner

-Valtren- wrote:

Dogs-are-amazing1 wrote:

Ty, but what goes in the space after the +?

(() + (0))

Depending on how well it works, I might close this, possibly

that's the costume offset. Say you wanted to animate from costume 50 to costume 80, you would code the below:

reset pro gamer timer :: custom
repeat until <[79] <(costume [number v] :: looks)>
switch costume to (((Pro gamer timer) * (30)) + (50))
end

This would switch the costume until costume 80, and do so in an FPSI manner

Ok, thank you

-Valtren- wrote:

A few workarounds:

Here's a standard method.

repeat ()
next costume
wait ((1) / (Desired FPS)) secs
end

Here's a slightly more complicated workaround, but it's reliable and even better isn't affected by lag.

-OdysseyCentral- wrote:

it would help meme makers with making their memes fpsi

Not really. This is for costumes. I am unaware of how it would affect motion blocks, but I don't think it would help a lot in that manner. A better method would be FPSI easing or cached tweening anyway.

Nvm

-Valtren- wrote:

A few workarounds:

Here's a standard method.

repeat ()
next costume
wait ((1) / (Desired FPS)) secs
end

Here's a slightly more complicated workaround, but it's reliable and even better isn't affected by lag.

-OdysseyCentral- wrote:

it would help meme makers with making their memes fpsi

Not really. This is for costumes. I am unaware of how it would affect motion blocks, but I don't think it would help a lot in that manner. A better method would be FPSI easing or cached tweening anyway.

I think I’ll put these in the workaround part of my post

Bump

I did not expect to be blinded by 3.0 colors stop

wikibro300000 wrote:

dup

I'm kinda confused, but this sounds like it's meant for costumes, while that's a reporter block?

Thanks for the good workaround.

Bump

medians wrote:

I did not expect to be blinded by 3.0 colors stop

wikibro300000 wrote:

dup

I'm kinda confused, but this sounds like it's meant for costumes, while that's a reporter block?

This is a block that changes the frame rate of costumes. So instead of going after 1 second, it goes by 15 or something per second. I think that’s how frames work, maybe

Dogs-are-amazing1 wrote:

medians wrote:

I did not expect to be blinded by 3.0 colors stop

wikibro300000 wrote:

dup

I'm kinda confused, but this sounds like it's meant for costumes, while that's a reporter block?

This is a block that changes the frame rate of costumes. So instead of going after 1 second, it goes by 15 or something per second. I think that’s how frames work, maybe

No it's not, that suggestion is for a block that reports the FPS, not changes the FPS.