handling asset management

i haven't used C2 for many months but I see that new developments in 3rd party wrappers like Nodekit have made C2 a very interesting development option.

how do you guys handle asset loading/unloading in big projects where the artwork is massive?

thanks

The Construct 2 engine handles this for you. When WebGL is enabled it loads textures layout-by-layout, and without WebGL the browser evicts unused textures on a last-recently-used basis.

very interesting.

so we just have to pop a sprite showing "loading" before the layout starts, and kill it first thing the layout is executed.

I've been meaning to bring up this issue again, as there has been reports of problems with long loading times for the game 'our darker purpose' of up to 5 minutes: http://www.scirra.com/forum/forum_posts.asp?TID=79206&PID=497902&title=our-darker-purpose-has-launched-on-steam#497902

As such I want to reiterate the importance of having control over the way C2 loads assets, as I described here: http://www.scirra.com/forum/forum_posts.asp?TID=83807&PID=489467&title=suggestion-load-the-necessary-images-of-layout#489467

Ashley - please consider adding this! Loading everything at the start into RAM is not optimal for all games. You could have it as an option so only advanced users would use it, if you're concerned about confusing newer users. Many, many pro games do this sort of thing, and with the extra controls we could do things like make loading screens ourselves and make the game start faster as we control the rest of the game loading in the background while the player plays.

loading all assets at the very start will make using C2 unfeasible for my project. We need some kind of control what assets to load and what assets to flush out