[ts][pixi-v8] Textures rendering issues.

[bookov]

Hi guys!
I'm currently migrating from pixijs/spine-v8 to spine-pixi-v8, and I'm encountering a peculiar rendering issue. It primarily affects animation sequences, but sometimes appears in static display objects attached to Spine.
My environment:

-     "pixi.js": "^8.6.6",
-     "@esotericsoftware/spine-pixi-v8": "^4.2.70", 
-     "@assetpack/cli": "^0.8.0",
-     "@assetpack/core": "^1.2.3",
-     Spine editor: 4.2.38 PRO, launcher: 4.2.13
-     Export of a single .atlas with multiple spritesheets, skeleton and stuff is generated in .json format

Problem: When Spine animations are rendered, they appear as a series of odd squares with incorrectly cropped textures. This problem occurs consistently across different animations and atlases. Although the texture coordinates and spritesheet IDs are correctly specified in the .atlas, the renderer crops the texture from the wrong spritesheet.

Example from the .atlas file:

main_3.webp
size:2046,1914
Fx/some/name_02
bounds:1095,1335,186,150
offsets:53,94,300,300

Instead of cropping from main_3.webp, the renderer uses the first spritesheet (main.webp), preserving the bounds, offsets, and rotation but applying them to the incorrect sheet.

import { Spine } from '@esotericsoftware/spine-pixi-v8';

const spineComponent = Spine.from({
  skeleton: 'path/to/skeleton.json',
  atlas: 'path/to/atlas.atlas',
});

// Add spineComponent to the stage and render

This would be amazingly awesome if you could help with this issue!

[davidetan]

Hello!

We have an example featuring sequences with multiple textures, and we've never encountered this issue. I'd be happy to assist you, but I’ll need a way to reproduce the problem.

Could you share a reproduction project demonstrating your issue? Alternatively, you can send your assets either here or to [email protected].

[bookov]

Thank you for looking into this! Unfortunately, due to an NDA, I’m unable to share project files or assets publicly. I will reach out to you at [email protected] so we can discuss the details privately. Thank you for your understanding!

[davidetan]

Sure, please link this issue to make it easier for us to process your request.

[davidetan]

The issue is confirmed and we're currently investigating it.