Something that shows the FPS of the current project, un-rounded however.
The FPS would fit into “Sensing”

(Frames Per Second)

Sorry, it would be more like this:

FPS:: Sensing

But an oval. I dunno how to do that with scratchblocks

Support.

Is this what you want?

(FPS :: sensing) // maybe with a checkbox next to this
show FPS :: sensing
hide FPS :: sensing

kenny2scratch wrote:

Is this what you want?

(FPS :: sensing) // maybe with a checkbox next to this
show FPS :: sensing
hide FPS :: sensing

Oh that's how you do it. Thanks man!

No support due to the fact that their are multiple existing workarounds that could easily be done by you or anyone else suggesting these blocks. Just search around the scratch wiki a while

ateesdalejr wrote:

No support due to the fact that their are multiple existing workarounds that could easily be done by you or anyone else suggesting these blocks. Just search around the scratch wiki a while

Okay, but that's not that point. Defining an FPS variable is useless waste of time for everyone. Not only that, but most of the methods put your FPS up to 1000 to infinity. Or what if I wanted to do a 1s1s that showed FPS? I don't want to have to search up how to pull FPS from a scratch project everytime I want to show FPS, and I don't want to memorize a script that would do the same thing as just a same

(FPS::sensing)

Cuffrox wrote:

ateesdalejr wrote:

No support due to the fact that their are multiple existing workarounds that could easily be done by you or anyone else suggesting these blocks. Just search around the scratch wiki a while

Okay, but that's not that point. Defining an FPS variable is useless waste of time for everyone. Not only that, but most of the methods put your FPS up to 1000 to infinity. Or what if I wanted to do a 1s1s that showed FPS? I don't want to have to search up how to pull FPS from a scratch project everytime I want to show FPS, and I don't want to memorize a script that would do the same thing as just a same

(FPS::sensing)

That's what a backpack is for And custom blocks help a ton! The reason it shows infinity by the way is because none of you use mainloops.

ateesdalejr wrote:

Cuffrox wrote:

ateesdalejr wrote:

No support due to the fact that their are multiple existing workarounds that could easily be done by you or anyone else suggesting these blocks. Just search around the scratch wiki a while

Okay, but that's not that point. Defining an FPS variable is useless waste of time for everyone. Not only that, but most of the methods put your FPS up to 1000 to infinity. Or what if I wanted to do a 1s1s that showed FPS? I don't want to have to search up how to pull FPS from a scratch project everytime I want to show FPS, and I don't want to memorize a script that would do the same thing as just a same

(FPS::sensing)

That's what a backpack is for And custom blocks help a ton! The reason it shows infinity by the way is because none of you use mainloops.

That again leaves us with the issues of 1s1s, and wasting of time and space. I can see where you're coming from but having an FPS object would make things much quicker and more efficient.

A frame is 1/30th of a second usually. I think that it can't know when you've finished renderring the frame, so maybe it should have a block:

Frame rendered::sensing

So that it knows when your frame has finsished?

ateesdalejr wrote:

No support due to the fact that their are multiple existing workarounds that could easily be done by you or anyone else suggesting these blocks. Just search around the scratch wiki a while

Workaround please? I know of none that are hard to do (and don't show your exact framerate).

Support

humantorch01 wrote:

Support

Why?

It already was on 3.0 prototype
It means probraly this suggestion already exists.

Yar workaround.

forever
set [timerprev v] to (timer)
do everything you need to here ::grey
set [FPS v] to ((1) / ((timer) - (timerprev)))
end

By the way, the workarounds generally find ticks per second, not frames per second. A tick is basically Scratch going through all the blocks and running the blocks it should. If you don't have any blocks that delay a tick, you're going to get tons of ticks per second.

when flag clicked
forever
  fps calculation stuff :: custom
  wait (0) secs // add this!
end

That should probably get you a more realistic frames per second.

Alberknyis wrote:

Yar workaround.

forever
set [timerprev v] to (timer)
do everything you need to here ::grey
set [FPS v] to ((1) / ((timer) - (timerprev)))
end

I would actually do this:

forever
set [timerprev v] to (timer)
do everything you need to here ::grey
set [FPS v] to (round (((1) / ((timer) - (timerprev)))))
end

MeIoetta wrote:

It already was on 3.0 prototype
It means probraly this suggestion already exists.

3.0 Prototype huh? Hopefully they don't change too much :L

ateesdalejr wrote:

humantorch01 wrote:

Support

Why?

Because it would be helpful

humantorch01 wrote:

ateesdalejr wrote:

humantorch01 wrote:

Support

Why?

Because it would be helpful

The workarounds they are whispering to me in my head.