On Demand Loading Issues

Bugsy

Hey guys, just running into some issues when attempting to export spine for on-demand loading with each skin having its own sprite atlas.

The specific issue we are running into is that the region names that are contained within the json contain the folder name for example

ninja/ninja-arm
ninja/ninja-leg

but the ninja atlas regions are named

ninja-arm and
ninja-leg

so it doesnt recongnize when importing.

We've tried using the flatten paths toggle but that doesn't actually remove the folder name from the region name.

Any tips on how we are approaching this would be super useful, thanks in advance

Spinebot

To address the issue of mismatched region names between your JSON and atlas files, you should ensure that the paths used during the export process are consistent. When exporting, if you want to remove the folder names from the region names, you should avoid using the "Flatten Paths" option, as it may not work as expected in your case. Instead, you can manually adjust the paths or use a script to ensure that the paths in your JSON and atlas files match. Additionally, you can consolidate your images into a single folder and adjust the image paths in your project to ensure consistency. This approach should help in aligning the region names in your JSON and atlas files for successful on-demand loading.

Bugsy

Spinebot Is there anyway that doesnt require manual editing of json files?

Harald

Bugsy Yes, Spinebot mentioned that in the middle of the paragraph:
Additionally, you can consolidate your images into a single folder and adjust the image paths in your project to ensure consistency. This approach should help in aligning the region names in your JSON and atlas files for successful on-demand loading.

Admittedly the text is a bit vague and likely only understood when you already know this answer. Perhaps this recent posting helps which answers the same question:
https://esotericsoftware.com/forum/d/28961-hi-colored-emission-maps/9

Harald

when attempting to export spine for on-demand loading with each skin having its own sprite atlas.

@Bugsy Also note that you don't necessarily need to have a separate atlas for each skin. It's sufficient to have separate atlas pages for each skin (also done via packing by folder structure), which results in a single .atlas.txt file but multiple material and .png texture assets, which each can then be loaded individually on demand.