Why Two Spine Atlas Regions Share the Same Coordinates

Two props have different asset names, but their regions point at the same spot on an atlas page. Check whether each name resolves and displays correctly before treating the shared rectangle as a missing asset.

Pack the same input with Alias on and off

The official Spine reference describes Alias as packing pixel-identical images only once. Give two inputs different names but the same dimensions and pixels, and include them in the same pack. Keep scaling, trimming, rotation and output settings fixed. Save the atlas data and page images from both runs.

For each region, record its lookup key, page, bounds and rotation. Load the correct files together and render both names. If each lookup works and both visuals match, sharing the rectangle is consistent with deduplication. If only one name works, inspect paths and name normalization in the importer before changing the art.

Change one visible pixel

In a test copy, modify a pixel well inside the visible area and run the pack again without renaming either file. Make sure the change survives the export settings, then check both keys with the newly exported data and page images. This control makes it easier to tell whether an unexpected match comes from the input, the pack or an old cached page.

Report the resource checks separately

The Texture Packer is the site's atlas packing entry point. Run the Alias comparison in Spine's Texture Packer, where that setting is documented. Record the page count and bytes with the lookup results. For rendering performance, use the related diagnostic guide to measure draw behavior in the receiving engine.