instead of 60 fps they could do interpolation


if you dont know what that means basically projects still update at 30 fps but they run at 60

for example doing

move (10) steps

with interpolation on would do

move (5) steps

twice over the course of 2 frames making it so the result is still 30 fps but it shows movement in 60 fps

Bump because of a dupe + consistency!

Yes 100% this would help a lot of laggy games that need turbowarp, and also for people who have it blocked in there school

nice

This?

ooo YES
THAT WOULD BE GODLY

Would this also work in fullscreen? This has probably been answered. And why does this feel like I'm upside down, or my head is upside down ,this hurts, real bad. I need a break. I'm sinking. Why? This is not a joke, I feel weird, eyes hurt.

alexandretherrien wrote:

MeIzAwezomeDede wrote:

Full support. I'd much rather have this than having to put a TurboWarp link in the instructions and hoping people actually click on it to properly play the project.

Yes and a lot of new scratchers don’t know what turbowarp is and they often think that it’s just turbo mode. It would be simpler if we did not have to use a different site to run games/animations without any lag.

Not gonna lie, I’m a fairly new Scratcher, and this would REALLY help my already slow iPad. It sucks Turbowarp is for some reason blocked on this thing!

Support. Also add some extensions from turbowarp (not all).

MeIzAwezomeDede wrote:

Full support. I'd much rather have this than having to put a TurboWarp link in the instructions and hoping people actually click on it to properly play the project.

You can use this block:

Is turbowarp?::boolean 

I don't know where I stand on this. It would be great for Scratch projects that lag a lot (like most 3D projects), and for people who can't access turbowarp. However:
1. Turbowarp already does this- it actually says that the compiler is disabled by default in the editor when you click on it in the advanced settings
2. There is another Scratch mod, called forkphorous that predated Turbowarp and does the same thing
Also, it's kind of fun to try to make projects that can run on Scratch quickly without the help of Turbowarp (or even turbo mode) running at 60 frames per second.

that's cool

just use turbowarp in the first place duh

LinkRevali wrote:

just use turbowarp in the first place duh

Some people have Turbowarp blocked

Anyways, support, this would be a neat idea so I can enjoy big projects without having to save it, then load onto Turbowarp

Support, this would get my slow projects faster

This would be helpful, but would practically erase all need for Turbowarp itself, and would be a big hit for the people who run it.

A good idea in theory but would make debugging more difficult though. The current system allows you to edit code while running but after compliing it with Turbowarp you need to restart the project.
If that issue can be solved then it would be great to have this in scratch

LionCoder10 wrote:

just use turbowarp in the first place duh

turbowarp is blocked for me, and lots of others

BigNate469 wrote:

I don't know where I stand on this. It would be great for Scratch projects that lag a lot (like most 3D projects), and for people who can't access turbowarp. However:
1. Turbowarp already does this- it actually says that the compiler is disabled by default in the editor when you click on it in the advanced settings
2. There is another Scratch mod, called forkphorous that predated Turbowarp and does the same thing
Also, it's kind of fun to try to make projects that can run on Scratch quickly without the help of Turbowarp (or even turbo mode) running at 60 frames per second.

Yeah but many people only have access to scratch, or have guardians that aren't comfortable with addons or turbowarp. Also as someone who's spent hours trying to make a MAP I hosted lag less by editing code I can personally say that trying to make projects run faster is an extreme pain.

Support.

It seems quite plausible that they could do this. And when transitioning to the editor they could just save the memory state and translate that into the regular project running thing I reckon. Might be complicated, but definitely worth it.