0 Favourites

Texture Atlas images not filling up - unexpected behaviour

  • Hi evryone,

    I have a project containing many 2-squared sized images like 128x128 and 256 by 256, all of them same type like png32.

    On export C2 creates 512x512 or 1024x1024 texture atlases but leaves complete rows empty. Instead adds another atlas image, also more than half empty!

    I really though and still think that a 1024x1024 should be filled completely with 4x4 images of size 256x256, but it just won't do it.

    Is this a bug? Or does anyone knows the reason for this? It's wasting my memory. And I want to fix it because of mobile performance issues.

    Any hint is appreciated. Thanks.

  • Create a dummy project that shows the issue, and post it to bugs.

    Keep in mind that if there aren't enough textures to fill the atlus it may leave some empty.

  • Hi evryone,

    I have a project containing many 2-squared sized images like 128x128 and 256 by 256, all of them same type like png32.

    On export C2 creates 512x512 or 1024x1024 texture atlases but leaves complete rows empty. Instead adds another atlas image, also more than half empty!

    I really though and still think that a 1024x1024 should be filled completely with 4x4 images of size 256x256, but it just won't do it.

    Is this a bug? Or does anyone knows the reason for this? It's wasting my memory. And I want to fix it because of mobile performance issues.

    Any hint is appreciated. Thanks.

    Tiled backgrounds are not combined together (maybe to avoid seams), and only pictures belonging to one sprite are spritesheeted together, also sprites have a 1 pixel added around them during spritesheeting to avoid seams.

  • Construct 3

    Buy Construct 3

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

    Buy Now Construct 3 users don't see these ads
  • Thanks for the replies... they cleared it up things a bit for me.

    It's obviously the one pixel added around sprites which makes things different than I expected. Of course 4 x 258 will not fit in a 1024.

    I suggest there could be an option to turn off the pixelborder on a per image/sprite basis.

    The other thing is that images from one single animation will not be separated into two (or more) eg 256 x 256 smaller spritesheets but instead be joined into a larger one (eg 1024 x 1024), even if obviously leaving empty half (or more) of this quite large spritesheet.

    For know I think I can work around it even not with perfect results. And I know texture atlases are a complex issue. Some manual tweaking options would be great. Hope there will be something in C2 in the future

    Cheers!

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)
Similar Topics Posts Views Last Post
Unread hot topic
0 Favourites
[BEHAVIOR] Chipmunk Physics
673 82,537
nelostic's avatar
nelostic
Unread hot topic
0 Favourites
[Behavior] LiteTween
672 169,975
manujorgo's avatar
manujorgo
Unread hot topic
564 105,259
rexrainbow's avatar
rexrainbow