[Performance][Bug] Animation Text extension with stamp and turbomode impacts performance

[098orin]

Animation Text extension with stamp and turbomode impacts performance.
Try the sb3 below.
https://github.com/098orin/sb3s/raw/refs/heads/main/tw-issue/Bad_performance.sb3

For busy people:

Be aware: I'm not proficient in English, so I may use incorrect expressions.

[098orin]

Note: The issue only occurs when the size is not 100%.

[098orin]

Here is a direct url
https://experiments.turbowarp.org/next/?project_url=https://raw.githubusercontent.com/098orin/sb3s/refs/heads/main/tw-issue/Bad_performance.sb3&turbo

[LegoBrainBiker]

It is possible that it is running multiple times per frame?
either way, this is most likely an issue with stamp, not animated text.

[LegoBrainBiker]

why do you need turbo mode for your project?

[LegoBrainBiker]

you could add a wait (0.001) seconds block.

[GarboMuffin]

Wait block won't help, this is an extension bug where the stamp and regular sprite rendering are requesting different sizes of the text costume in an alternating pattern. Each one of those requests that is causing the text to be redrawn and uploaded to the GPU since the size doesn't match the cached texture

fixes to consider:

• mip levels like vector costume
• re-render only when requested resolution is larger; if smaller resolution requested just return the bigger texture already drawn

[LegoBrainBiker]

Wait block won't help, this is an extension bug where the stamp and regular sprite rendering are requesting different sizes of the text costume in an alternating pattern. Each one of those requests that is causing the text to be redrawn and uploaded to the GPU since the size doesn't match the cached texture

it seems more likely that the issue is that it is being called multiple times per frame for some reason. the issue only occurs in turbo mode, and the fps block still displays 30. only the screen refresh rate is affected. what your describing may cause some performance issues, but it seems like somthing more is happening.

[LegoBrainBiker]

I would like to be clear, this is a turbo mode bug, it does not occur without turbo mode enabled. and the wait block did fix it.

[098orin]

Certainly a wait block can help solve this problem, even if the wait is so short that it is negligible.

[GarboMuffin]

Ok, thanks for suggesting me to dig a bit deeper

The wait block fixes it by making turbo mode effectively not do anything so sure you can do that. If you want your project to only stamp once per frame in turbo mode instead of taking up the entire frame budget stamping the same costume over and over then this is a good idea anyways regardless of this issue being fixed

There's another problem in the renderer with stamps also causing a similar problem of requesting a 1x resolution and then the actual correct resolution immediately after each other TurboWarp/scratch-render#16. That does affect regular Scratch too but vectors store multiple mips so it would only stutter once