It sounds like you are experiencing an issue with the visibility and rendering order of your Spine assets in your game. This could be related to how the assets are being loaded and managed in your game engine. One possibility is that the Spine asset is not being properly hidden or its visibility state is not being correctly initialized, which causes it to flash or appear unexpectedly. Additionally, the issue with the game background might be related to how the rendering order or layers are set up, causing the Spine asset to appear on top of the background when it shouldn't.

To troubleshoot this, you can try the following steps:

1. Ensure that the Spine asset's visibility is explicitly set to invisible at the start of the game or when it should not be visible.
2. Check the rendering order or layer settings to ensure that the Spine asset is not being rendered on top of the background when it shouldn't be.
3. Verify that the assets are being loaded and initialized correctly, and that there are no conflicts or overwrites happening with the keys used for loading.
4. Consider adding debug logs or breakpoints to track the visibility state and rendering order of the Spine asset throughout the game's lifecycle.

If these steps do not resolve the issue, it might be helpful to provide more specific details about the game engine you are using and how the assets are being managed.

Hello!

To assist you effectively, we need the following information:

• The runtime and version you're using (e.g., spine-phaser 4.2.68)
• The version of your exported assets, as well as the editor version used

Since your issue appears to depend on your configuration, providing a minimal reproduction project would be very helpful. You can share it here or send it to us at contact@esotericsoftware.com.

mevan

and I didn't get what I need to send for version of exported assets. Is it the spine export version ?
Yes, exactly, the version mentioned here.

But, as I told you I cannot reproduce the issue you described. Any chance you can send a project that I can run to debug the issue?