Loading sprite sheets when using a loader layout

0 favourites
  • 4 posts
From the Asset Store
With this template you will learn how to use the GooglePlay Games native plugin
  • Hello, I am using loader layout to display the loading screen. I only left a few sprites on it for a nice look. But here's the problem - when assembling sprite sheets after export, the sprites from the loading screen are packed together with the rest of the sprites. And because of this, large sprite sheets are created, about 3MB in size, and these sprite sheets have to be loaded at the very beginning in order to reach the loader layout. As a result, half of the game is already loaded before the loader layout appears. And half the time the player looks not at a beautiful loading screen, but at an empty one (there is now a white background and a logo).

    There is not a word in the documentation about sprite sheets, but only a reminder not to load the layout loader with a large number of sprites and animations.

    I would like to know if there is a way to fix this?

    p.s. Usually in games the logo appears at the very beginning for a second, and then the entire game loads. I don't want to use two different loading screens in the game (splash screen and loader layout). Percentages at the beginning or a splash screen that is difficult to change through the source code. And, of course, I didn’t want to wait for half the game to load in order to see the loading screen

  • This is a very relevant issue for WEB games, I haven't found a solution and just change the "loading-logo.png"

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I would like to clarify, of course. When exporting, how hard is it, when "loader layout" is enabled, to assemble sprites from the loading screen into a separate sprite sheet? Because the engine understands which sprite sheet contains the sprite from the loading screen and loads it first. But this is more of a question for Ashley.

  • One of the fundamental tradeoffs of spritesheeting is it bundles images together and can only load them all at once. You can change the maximum spritesheet size in Project Properties - smaller sizes will tend to fragment things in to more spritesheets and so avoid having to load other content, but ironically it can also increase the download size. Large spritesheets allow image compression to remove repeated image content and so can be better for reducing the download size. At the extreme you can disable spritesheeting (in the latest beta) which will load precisely the right content, but also make it a much bigger download. So you may be trading off showing the loader layout sooner, for showing the loader layout longer. Spritesheeting is full of tricky tradeoffs like this.

    If your entire game is only 6mb, I don't think there's much benefit to using a loader layout anyway - these days the average web page is over a 2mb download, so about three times the size of a web page probably isn't that long a download for most people.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)