Displayables with changing children jitter when physical size is less than ~75% screen size about renpy HOT 5 OPEN

More information after some additional testing:

if I only use 3 different images in the transform, like so:

image phylla_title:
    "cg/title/phylla_title_00.png"
    1/8
    "cg/title/phylla_title_01.png"
    1/8
    "cg/title/phylla_title_02.png"
    1/8
    "cg/title/phylla_title_00.png"
    1/8
    "cg/title/phylla_title_01.png"
    1/8
    "cg/title/phylla_title_02.png"
    1/8
    "cg/title/phylla_title_03.png"
    1/8
    "cg/title/phylla_title_02.png"
    1/8
    repeat

Regardless of hte order and how many times, it doesn't seem to jitter (the jittering offset seems tied to the specific image/frame)

Additionally, if I duplicate one frame 8 times and name them all differently, again, no jittering. (in this example, #s 08-14 are exactly the same as 00, but separate files)

image phylla_title:
    "cg/title/phylla_title_00.png"
    1/8
    "cg/title/phylla_title_08.png"
    1/8
    "cg/title/phylla_title_09.png"
    1/8
    "cg/title/phylla_title_10.png"
    1/8
    "cg/title/phylla_title_11.png"
    1/8
    "cg/title/phylla_title_12.png"
    1/8
    "cg/title/phylla_title_13.png"
    1/8
    "cg/title/phylla_title_14.png"
    1/8
    repeat

Lastly, if I ONLY use frames I know have a jittered offset, the offset IS there. I assume this means it's something about the actual data of the images causing this?

Again, this only happens when the window is scaled down smaller than about 75% of virtual size..

from renpy.

Do you have an example game? Simply postying code isn't going help, as I'd need to see if it's an issue with the images.

from renpy.

I will make up a small example.

from renpy.

Here you go.
https://www.dropbox.com/scl/fi/q1nalujzx6x9b7qbkj0lt/TestingGrounds-1.0-pc.zip?rlkey=vv5rv6zjpix8d7uo0jdsjbjtl&dl=0

Super empty game, just has the sprite and showcases the problem.
The script resizes the screen as you play through, to show the issue.

from renpy.

I've figured out a way to stop this from happening. Adding mesh True to the transforms for the images keeps this from happening.

Still seems like it's an error (and if for whatever reason someone can't use mesh True, it would still be a problem), but it works for my needs.

from renpy.