Discuss Scratch
- Discussion Forums
- » Questions about Scratch
- » Lag is ruining projects
- acedannyk
-
Scratcher
100+ posts
Lag is ruining projects
I'm sorry for the bluntness of this post but I want to be brief. Lag is ruining scratch projects which are otherwise great. Before the site update these projects ran almost perfectly. I've heard this is a Chrome exclusive problem but I find that difficult to believe since a player of one of my games described lag problems identical to those in Chrome when using Firefox as their browser.
The simple question I want to ask is will these issues be addressed? Thanks in advance and keep up the good work.
The simple question I want to ask is will these issues be addressed? Thanks in advance and keep up the good work.
- andre_rifaut
-
Scratcher
100+ posts
Lag is ruining projects
I the meantime, you could see what is making the project lag.
For instance I discovered that “wait <condition>” is very costly. So, now I translate that with an “repeat until <condition>” with a “wait 0.1 sec”
In summary it might happen that cycles are less costly to run than before, so more time is left for executing what is inside the cycles which could be very much costly and do not let time to switch the execution between different sprites or different blocks, …
Indeed, it is difficult to tune any interpreter …
For instance I discovered that “wait <condition>” is very costly. So, now I translate that with an “repeat until <condition>” with a “wait 0.1 sec”
In summary it might happen that cycles are less costly to run than before, so more time is left for executing what is inside the cycles which could be very much costly and do not let time to switch the execution between different sprites or different blocks, …
Indeed, it is difficult to tune any interpreter …
- acedannyk
-
Scratcher
100+ posts
Lag is ruining projects
For instance I discovered that “wait <condition>” is very costly. So, now I translate that with an “repeat until <condition>” with a “wait 0.1 sec”I can't quite understand what you mean by your second sentence. I understand what the blocks are but I can't see how the “repeat until” block ties in with the time delay.
- letmethink
-
Scratcher
100+ posts
Lag is ruining projects
For instance I discovered that “wait <condition>” is very costly. So, now I translate that with an “repeat until <condition>” with a “wait 0.1 sec”I can't quite understand what you mean by your second sentence. I understand what the blocks are but I can't see how the “repeat until” block ties in with the time delay.
He means that instead of the ‘wait 5 seconds’ block' you can use the ‘repeat until’ block with ‘wait 0.1 seconds’ inside to prevent lag; at least that it what I think he means.
- acedannyk
-
Scratcher
100+ posts
Lag is ruining projects
My project has over 200 scripts and not one of them contains a time delay. I double checked everything. The lag is not just an inconvenience - it completely destroys the game and renders it totally unplayable past a certain point. People complain every day about lag issues that I just can't fix. I never got an answer as to whether the scratch team ever plans on addressing the problem. It'd be great to know.
- Discussion Forums
- » Questions about Scratch
-
» Lag is ruining projects