Just a quick question I need answered:
What effect does the number of sprites in a project have on the performance of the project?

I think the code that runs (including how many scripts there are, and blocks in those scripts) matters more than the number of sprites, unless there are tons of them that are visible. In that case it will have to spend time rendering all of them, but I don't think hidden sprites affect rendering performance much.

H2OtastesGood wrote:

Just a quick question I need answered:
What effect does the number of sprites in a project have on the performance of the project?

I don't think it has much, pen projects with only one or 2 sprites lag like crazy due to all the pen and math contained in them

Also you can convert sprites to bitmap

removed

Technically yes, but having one sprite versus four is going to make such a minimal difference it’s jot worth your time to compress it into one sprite, unless you’re doing something such as the 1S1S challenge.

2006kush2010 wrote:

Also you can convert sprites to bitmap

Does converting sprites to bitmap improve performance?

H2OtastesGood wrote:

2006kush2010 wrote:

Also you can convert sprites to bitmap

Does converting sprites to bitmap improve performance?

No as all it does is change the costume to bitmap (PNG) from vector (SVG), which is unrelated from the performance. By the way, the performance is based off the number of blocks and the intensity of the blocks on the computer.

H2OtastesGood wrote:

2006kush2010 wrote:

Also you can convert sprites to bitmap

Does converting sprites to bitmap improve performance?

No it could potentially create more lag as every single pixel has to be displayed instead of a vector (which consumes less bytes)

WallydogChoppychop wrote:

(#10)
No it could potentially create more lag as every single pixel has to be displayed instead of a vector (which consumes less bytes)

False, vector still has to be converted to bitmap to be displayed, and if you're changing the sprite's size or using fullscreen the vector also has to be converted to bitmap and stored into memory for each size.

Flowermanvista wrote:

(#4)
It might take up less storage space, but it will take up a lot more RAM when playing back. Whenever a vector is displayed for the first time, Scratch caches the bitmap it rendered from that vector uncompressed in memory - and that bitmap will be very big if it was rendered when the project was in fullscreen. If Scratch is fullscreen on a 1080p monitor, a vector that takes up the entire canvas will use about 4 MB of RAM when it's displayed - a 15 fps animation would suck up 62 MB of RAM per second.