Compiling - Spritesheet causing seams

0 favourites
  • 7 posts
  • When I tile my sprites together, there'll be seams around the sprite edges. It doesn't happen in preview mode, only happens after exporting.

    I've tried pixel rounding, point sampling and letterbox integer scale. Nothing seems to properly. They just reduce the seams, but there are still random visible lines in the background.

    My sprites are all 512x512 so in older C2 versions they don't get packed into sprite sheets and everything's pixel perfect. This problem came up after the 2048x2048 and 1024x1024 sprite sheet implementation.

    Is there anyway I can prevent my animation frames from packing into sprite sheets? Or any other ways to solve this?

    Thanks in advanced.

  • Post a .capx - those settings should make it work fine.

  • Hi Ashley,

    Here's the link to the capx.

    Here's the link to the exported version.

    Maybe the problem lies with the scaling?


  • It doesn't seam in Chrome, IE or Firefox here, either in preview or in export. Looks fine.

    However there's no point cutting it in to 512x512 tiles - you may as well have one big image. It's just up to the maximum widely supported texture size of 2048x2048.

  • I think your screen size is too big. It usually happens when scaling down. I'm viewing it on a 13" laptop screen 1366x768 resolution.

    The seams usually disappear when you up your screen resolution or screen size, but we cant guarantee everybody have such big screens or resolution.

    Here's a screenshot.

    The reason why we cut BG images up is because we have some border backgrounds with alot of empty spaces in the middle. So cutting them up will save a lot of wasted memory. Smaller tiles usually can save more memory for odd shaped borders.

    Also if the image is 2048x1536, it will waste 2048x512 of memory. So, its become a common practice for us now to cut them into 512x512.

  • It was scaled down, and I still didn't see any seams.

    Seams can be tricky to avoid especially with floating point position/scale. You might use more memory but making a single texture will definitely not seam. Phones ship with 2 GB of memory these days, and a single 2048x2048 image will take up about 16mb of memory. As long as you don't have lots of them and aren't targetting really low-end devices, that's OK. If you still want to cut it up, square tiles isn't the best way to do it - a smarter way would be to cut out each item on the image (e.g. text, each building image, etc.). The background is a low-contrast gradient, which you can reproduce with linear sampling and scaling up a small sprite. That would probably use even less memory than the square tiles approach, it wouldn't seam, and you can then re-use the individual pieces of art throughout the project.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Yup, I guess we can try using alternative methods to avoid this problem, but the fact that is happens only when they are packed into spritesheet its kind of weird.

    Previously when they were individual images none of this happened. Maybe when extracting images from spritesheet there's some slight measurement error?

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