In that case maybe you could make an invisible tile-map over-top of the maze with enough tiles to properly represent its complexity. Or make the maze out of a tile-map in the first place.

Have you gone through the manual and tutorial entries on performance optimization for mobiles?

Like this one: https://www.scirra.com/manual/134/performance-tips

Luckily, recent NWjs builds no longer have memory leaks and performance is really good.

What about the issues with saving that some people were having with newer builds?

TGeorgeMihai, maybe I misunderstood but you seem to have the mistaken idea that nw.dll is included exports from Construct 2 intended for mobile.

Actually you're making me have to repeat myself. Again, you haven't created a 5mb game and then added a 60mb addition to it. The game is not 5mb at all, its 65mb. The dll file in question is just as much part of the game as any other included files.

I suppose the documentation could be amended to say something like "games exported with NW.js will be at least X mb", but there's always a trade-off when choosing what information to include or highlight.

You're determined to rhetorically divide the size of your final game into the regular content and the "additional" content from nw.js - in fact you keep using that word "additional" over and over again. But that breakdown seems arbitrary to me. All game builds will end up using some space for assets and other space for engine and engine libraries. Both are part of the game, neither is an extraneous addition. Scirra shouldn't really have to specifically point out that the engine will take up space any more than they should have to tell you the other assets (graphics, music, etc.) will.

I think maybe the reason I'm not seeing any nw.dll is because I haven't upgraded to the new alpha yet. Are the issues with saving in the newer NW alphas been solved or worked around yet?

Why is it that I'm not seeing this file that you guys have? Is it because I'm still using a win32 machine? Right now my entire game is under 130 mb, exported.

What made you think it would be released so soon? I'm expecting there's still a while yet to go.

At what point are you seeing those? You mean when you export the game or when you export individual sprites?

Shouldn't you wait til the next stable update of C2 to update your game?

tgeorgemihai

NW improved on memory management and working vsync, C2 is good even for bigger games. I just hope the situation remains good and improves. We do not want major chromium bugs to neuter C2 for months on end ever again. That's the biggest risk with C2, hoping that Google doesn't accidentally break your games.

Wouldn't the solution in that situation be simply to export without updating NW.JS?