I think scratch would benefit from having a higher refresh rate.

Pros: Smoother projects, benefit of monitors with high refresh rate.

Cons: I don't know how the engine works but if the tick rate is the same as the fps this could possibly break projects. EDIT: Someone said the projects would run faster if the fps was higher, so the engine would have to be reworked.

Zydrolic wrote:

Scratch is nonprofit.
The servers have loads of workload;
Engineering team smallened because of layoffs.

Discuss more cons and pros and tell me if the engine is dependent on 30 fps. Tell me if this topic is already discussed.

Optionally there could be a block changing the fps of the projects so you can cap it anywhere from 30 to 240.

EDIT: Brought this back, my brain died doing this so this is probably just wrong (about servers)


Scratch is nonprofit.
The servers have loads of workload;
Engineering team smallened because of layoffs.

Faster frame rate doesn't mean animation quality will be good most projects would not work

cs3868895 wrote:

Faster frame rate doesn't mean animation quality will be good most projects would not work

I'm guessing what you mean is that projects would just run faster instead of smoother.

arvepro3579 wrote:

cs3868895 wrote:

Faster frame rate doesn't mean animation quality will be good most projects would not work

I'm guessing what you mean is that projects would just run faster instead of smoother.

Yes. Many projects are frame rate dependent, thus, they break when ran in turbomode. Same would happen if framerate goes up to 240 fps

Support, but make it a block that has to be added to a project to enable unlimited or 240 fps mode. A more accurate timer would be necessary, one that works not synced to the frame rate but one synced the actual CPU's timer of the PC so that delta timing can be achieved as accurate as possible.

One con is that projects built around this wouldn't work as well, and possibly break.

Well, firstly, bumping up the framerates by 8 would make almost all projects unplayable. When you bump up the FPS by 2 (using TurboWarp), the project plays at 2x speed. Imagine the project playing at 8x speed!
If we could change the framerate without changing the project speed, I'd rather the project play at 60FPS. It's roughly 4x less taxing on your machine, and most monitors don't output at 240 Hz. The standard for monitors is 60 Hz, meaning that you won't see those extra 180 frames.

Currently, no support. If we changed the suggestion from “240 fps” to “60 fps”, support, the only problem would be projects running at 2x speed. We need a way to circumvent this.

This would just make projects WAY too fast. Try it with https://scratch-mit-edu.ezproxyberklee.flo.org/projects/676672653

And also it would break a lot of projects. So no support unless optional.

But I don't want to get confuzzled by 240 fps, and that is way too fast

ninjahanzo wrote:

But I don't want to get confuzzled by 240 fpp

How would you get confused by an FPS number?
this is the first time i have ever heard someone use the word “confuzzled”

sonic__fan wrote:

ninjahanzo wrote:

But I don't want to get confuzzled by 240 fps

How would you get confused by an FPS number?
this is the first time i have ever heard someone use the word “confuzzled”

if it was 240 instead of 30 i would be confused because it changed and scratch uses 30 fps
also the main point is 240 is way too fast

ninjahanzo wrote:

sonic__fan wrote:

ninjahanzo wrote:

But I don't want to get confuzzled by 240 fps

How would you get confused by an FPS number?
this is the first time i have ever heard someone use the word “confuzzled”

if it was 240 instead of 30 i would be confused because it changed and scratch uses 30 fps

oh ok

Support, but only if optional. Like mentioned before, some projects can break or lose their quality, however, it can also benefit them in many ways depending on the project type.

30 is a general common frame rate, and is what many devices use by default.
Increasing this would cause issues on mobile projects, although screen refreshes aren’t the only benefit of higher FPS’s. Higher FPS means lower latency in a lot of cases, as the program has to go through more iterations for one frame.

No support because it'll make my runner games impossibe and break some very sensitive projects. Also, 240 FPS sound like overkill and my tablet (My browser / operating system: Android 11, Firefox 117.0, No Flash version detected) can only got at 60 FPS max. However, if it could be controlled within the project itself, then support so I can make some of my projects automatically set the FPS to the number that should be used for the specific difficulty.

Use Turbowarp.

__Falcon-Games__ wrote:

Use Turbowarp.

Turbowarp only supports up to 60 fps.

arvepro3579 wrote:

(#18)
Turbowarp only supports up to 60 fps.

Goes up to 250 maximum.
EDIT: Would reccomend reading more…

id love this, but it would break most advanced projects as they rely on 30fps to time things instead of using seconds or something like that

in fact

wait (0) secs

waits one frame, this would also make projects with custom blocks lag more because its running the warp so much faster

also like 70% of all screens have a 60hz refresh rate, and im not 100% sure but i think web browsers are usally limited to 60hz as well

so really the best they could do is 60fps, that would make alot of sense as most programs tend to run natively at 60fps