Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Got totally addicted but should have read the comments first about the out of memory issue. This was a really cool take on the auto-clicker genre and I like the use of the helpful thing hurts you theme! 

Delighted you enjoyed playing! Sorry about the OOM error it's the biggest regret for me this jam. Still I've learned more about the limitations of WEBGL builds with Unity, so hopefully I can plan to avoid the same fate in future games. Thanks for playing!

Oversimplifying a bit but webassembly has a 4GB memory limit, and in practice you can't even use that much. Also unlike a desktop build, WASM builds can't move data from memory into swap space as they run out of RAM.

What I'm getting at is it's quite possible that you have a memory leak in the desktop build too, it's just much harder to run out of memory in that environment.

ah ok, thanks a lot for that. I’ll look into it. I’d gone through minimising texture sizes, minimising the shaders and materials used, all to no avail… so thanks for the help. 

If you want to get to the bottom of it, the most likely cause is some resource/class/object that you load or instance, maybe something you do every time you switch between scenes. If it's in your own code, you're looking for a logical error like a list you never clear.

(+1)

I’ll take a look, thanks!