It is really annoying, when you need put objects in layout for this.

This also requested: Jun 29 2019

construct3.ideas.aha.io/ideas/C3-I-978

Ashley

I tested your project on a Pixel 3 and got the following results:

C2: first switch ~232ms, later switches ~100ms

C3: first switch ~170ms, later switches ~100ms

So according to this, the C3 runtime is faster in this case. I don't know why other devices would be different, maybe specific hardware is better or worse in different cases.

Are you testing everything with high-end phones? We are trying to optimise our games for low end devices. Because everyone don't have good phones.

You can run this game smoothly with your device but other people can't, they don't have high-end phones.

I can say, I can't run this game too, so laggy with low CPU devices.

play.google.com/store/apps/details

Construct 3 supports Android 5+ but you trying everything Android 9+.

Besides, C3 has a new feature that helps you hide this from the user - there's a built in memory management action "Load layout images", so you can load the next layout's images in the background while the current layout continues to run, and then switching layout will be instant. This feature is not available in C2. If I use "Load Layout 2 images in to memory" on start of layout in Layout 1, then it can switch layouts in around 5ms, which is far faster than you can ever achieve in C2.

I give a thanks to Toby R and rexrainbow . They are good developers. They made good addons for us (Game Developers). Which you don't like that ideas.

Try this Example (My 2nd example I was posted)

construct.net/out

Just try one sprite and unload it from memory. That feature will not help you a lot. Because one sprite object using 1024x1024 png file. We can't edit, we can't move that sprites as a group. We don't have any access on spritesheeting. In this case Toby's MM Unloader plugin works better with C2. C3's memory features can't help you. It is all about spritesheeting, you know that. Also MM Preloader will help you load assets from another layouts, this will works perfectly because you can load with C2 what you want. C3 will load other assets from png file, which you can't unload.

Also people request good ideas, you was set status "declined"

Idea-1: construct3.ideas.aha.io/ideas/C3-I-638

Idea-2: construct3.ideas.aha.io/ideas/C3-I-104

So as far as I can tell C3 is both faster at loading layouts and it has a feature to help guarantee that layout switching will be instant, which works here.

No comment.

I made actual measurements and demonstrated it got pretty close to C2's memory use.

Thats my mistake (the first one), can you try everything with last example.

C2's max spritesheet size is hard-coded at 2048 and there is no option to change it. C3 has an option to change it, and smaller sizes tend to use less memory, so C3's 1024 setting can help.

We can do this (look at image) with Construct 2 but C3 don't allow and this what we need for mobile. You can see in example project. I use all object one frame. Because it is best way for memory optimisation with C2. C3 don't allow this it is using every time what you choose, lower option only 1024 and it is really big for mobile.

Please look image. Did you see they all only 256x256 px. And if sprite size lower than 256x256, C2 will export that images lower size too.

image: i.imgur.com/PGnfJoc.png

You can give us 64x64, 128x128, 256x256 options for mobile but not 1024x1024. You can see and you can try last apk, it doesn't help. Layout changes took 4-6 sec with 1024 option too.

Actually best option;

if sprite only one frame export it one file.

If sprite have a lot of frames than export it using max file size (what we choose, like 1024)

Ashley just add new project it is using also 1024x1024 option. You can choose what you want. It is good example to show you we don't have any control on spritesheeting with C3. But with C2 we can do something.

Just want to show you. (You know this already)

With Construct 2;

• If we use one frame sprites in project it is exporting only that sprite as (one).png file.
• If we have animated sprites in project this time it is exporting that frames using max spritesheet size (1024 for C2)

But we don't have any option for that with C3.

You can say use 1024 option. It is not really help on mobile.

Just made example for that. We don't have any control on sprite sheet exporting. with Construct 2 we can do something, but you know C3 don't have any option.

Layout changes really bad because it is using all assets which I don't use in layout. Because spritesheeting algorithm.

I hope you understand what we need now for mobile.

Just best option if we can choose that spritesheet exporting like C2's way.

Example:

drive.google.com/file/d/1ZW8XdsznXtuST-3vSrnBSAQxtluu2IIO/view