你好，

关于在Spine-Unity中使用换装功能的性能问题，以下是一些关键点：

1. 资源加载：如果你有大量的服装选项（如100件），建议不要一次性加载所有的图片。可以在运行时只加载当前使用的图片，并通过运行时重新打包（Runtime Repacking）来组织纹理。详细信息可以参考Combining Skins部分。

2. 性能测试：为了确定性能是否会受到影响，建议在目标设备上进行测试。你可以下载spine-unity runtime进行评估，并使用其中的示例骨架进行测试。下载链接：spine-unity Download。

3. 优化措施：常见的性能优化措施包括减少材质切换和绘制调用。你可以通过合并皮肤或附件到单一的纹理来减少这些操作。更多信息可以参考spine-unity Performance部分。

4. 动态重载：如果在运行时频繁更换皮肤，可能会导致性能下降。可以考虑在非关键时间点进行这些操作，或者分帧处理多个重载操作。

5. 示例项目：spine-unity runtime中包含一些示例项目，如“Mix and Match Skins”，可以帮助你了解如何在运行时组合多个皮肤。

总的来说，合理的资源管理和优化措施可以有效减少性能影响。

kodoly7 By default, the SkeletonDataAsset references the AtlasAsset, which references its atlas pages as Materials, where each Material references the atlas page texture. So if you exported all atlas pages normally as a single AtlasAsset, all pages will be loaded as soon as your skeleton's SkeletonDataAsset is loaded.

If you want to load atlas texture pages on-demand, you need to make sure to not include direct references and instead use Unity means of delayed-loading, such as Addressables. You can use a build script to clear any direct references to the delayed-loaded resources and use a loader script to load and assign references at runtime when actually used.

To make it easy, we provide convenient modules. To use them, download the two packages Spine On Demand Loading and Spine Addressables. For more information on how to install the extension packages, please see the documentation:
https://zh.esotericsoftware.com/spine-unity#%E5%8F%AF%E9%80%89%E7%9A%84UPM%E6%8F%92%E4%BB%B6%E5%8C%85

Also check the Spine Addressables documentation:.
EsotericSoftware/spine-runtimestree/4.2/spine-unity/Modules/com.esotericsoftware.spine.addressables/Documentation

The spine.addressables package utilizes Unity's Addressables package, which will be installed automatically through dependencies if not already installed in your project.

kodoly7 I'm afraid I didn't understand your question very well, perhaps because the machine translation didn't work very well. It would be easier if you actually tried it, but just in case, here are the steps to set it up for your reference:

1. Declare your original high-resolution target Material textures as addressable.
   

2. Select the SpineAtlasAsset, right-click the SpineAtlasAsset Inspector heading and select Add Addressables Loader.
   
   This generates an AddressableTextureLoader asset. This asset provides configuration parameters and sets up low-resolution placeholder textures which are automatically assigned in a pre-build step when building your game executable.
   

3. Build your Addressables content as usual.
   

@kodoly7 You need to install com.esotericsoftware.spine.on-demand-loading#4.2 first, before installing the com.esotericsoftware.spine.addressables package. So add the following package via git URL:
https://github.com/EsotericSoftware/spine-runtimes.git?path=spine-unity/Modules/com.esotericsoftware.spine.on-demand-loading#4.2

A description can also be found here:
EsotericSoftware/spine-runtimes1890

@kodoly7 Thanks for the additional info. The experimental on-demand-loading package currently has a dependency to the spine-unity UPM package, which is not detected by the Unity Package Manager when installed as unitypackage. So the solution would be to either uninstall the spine-unity package from the unitypackage and re-install it via the Unity Package Manager (spine-csharp and spine-unity), as described here.

An alternative would be to remove the dependency line

"com.esotericsoftware.spine.spine-unity": "4.2.21"

from the package.json inside the com.esotericsoftware.spine.on-demand-loading package directory. To be able to modify the package.json file, you might need to clone the spine-runtimes git repository to a local directory, and then modify the file.

We're sorry for the inconvenience!