Card game optimization and many animation frames in the sprite

Each animation contains 100-200 frames, and these are the same 105x131 images.

Just to clarify - the size is the same, but the images are different in each animation, right?

A quick test shows that 1000 frames with that resolution use about 80-85 MB in memory. So your game should probably run fine, even on mobile. But I would try to reduce the number of frames in animations, 200 frames feels like a lot.

> Each animation contains 100-200 frames, and these are the same 105x131 images.

Just to clarify - the size is the same, but the images are different in each animation, right?

A quick test shows that 1000 frames with that resolution use about 80-85 MB in memory. So your game should probably run fine, even on mobile. But I would try to reduce the number of frames in animations, 200 frames feels like a lot.

Yes, the size is the same everywhere, but the images are different. These images are different cards. I can't reduce them because my game is quite content-rich. And I give them complete freedom. The maximum I can do is cut down and use 170-180 animation images instead of 200. But don't forget about updates. Since the entire game is based on my cards, they're a core element in the game, and I plan to expand them.

I specifically bought a test phone and am using my old one. My game runs on an Oppo A3, which uses about 100 MB of memory, and lags a bit, but overall works. And on a Meizu Pro 7, I get artifacts and a white screen with a sad smiley face in the upper left—basically, it crashes. Basically, 100 MB is already pretty critical. Although my card images alone weigh 80, not counting the UI and other objects.

Maybe there's another solution? I tried asking the neural network, and they told me to split all the animations into separate sprites. But that doesn't change the essence of the problem if all these sprites are on the screen. It's the same thing.

Do you see that images only use 100 MB in the debugger? That's very modest memory usage, it should not crash a phone with 4GB of RAM. The issue must be with something else. Try collecting LogCat logs.

Yes, in the construct debugger

I found an old screenshot with a video recording where the game, while idle and without any additional actions, simply crashed after a while. It's a different project, but it has the same memory consumption of around 100 MB.

Yes, for me, that's a critical figure right now. Still, are there any recommendations other than improving the content in my game?

I'd definitely recommend separate Sprite objects rather than one Sprite object with tons of content on it. See memory usage - Construct's memory management either entirely loads all a Sprite object's animations, or unloads them all; if you have everything in one Sprite, it will either have everything loaded or nothing, but if you have everything in multiple Sprite objects, you can have just some of those loaded.

You can then add all those Sprite objects to a Family so you don't have to repeat events. You should be able to use 'Replace object' on your existing events with a Family so you don't even have to re-do the events.

And on a Meizu Pro 7, I get artifacts and a white screen with a sad smiley face in the upper left—basically, it crashes.

These are characteristics of graphics driver bugs. So it might be crashing due to a buggy GPU driver rather than running out of memory.

Construct's memory management either entirely loads all a Sprite object's animations, or unloads them all; if you have everything in one Sprite, it will either have everything loaded or nothing, but if you have everything in multiple Sprite objects, you can have just some of those loaded.

I'm also making a card-type game and I was looking for this information, it might be helpful to add this to the sprite page in the manual