I ordered spine skeleton animation to be applied as a set skin
The skin I want is definitely in the skin array variable
It applies well to all other skin types But one skin I want
It's a problem that only that skin isn't applied
Find a problem that only one skin isn't applied 2
If a specific skin is not being applied while others are working correctly, there are a few potential issues to consider. First, ensure that the skin name is correctly specified in your code and matches exactly with the name in the Spine project. You can verify this by checking the skin name in the Spine editor and comparing it with the name used in your code. Additionally, check if there are any warnings in the Spine editor when you open the project, as these might indicate issues with the skin setup. If the skin is present in the array but still not applying, it might be due to missing attachments or incorrect setup in the Spine project. You can also try setting the skin to null before applying the new skin to ensure that no previous skin settings are interfering.
I ordered spine skeleton animation to be applied as a set skin
The skin I want is definitely in the skin array variable
It applies well to all other skin types But one skin I want
It's a problem that only that skin isn't applied
What's so annoying that it's hard to explain is that when I used Construction script to call and test the skin in real time, not in simulation, it worked as intended. So I know there's no problem with the blue print or the skin, but when I test it in simulation, it doesn't show like a ghost
It sounds like you are experiencing an issue where a specific skin is not being applied correctly during simulation, even though it works when tested in real-time using a construction script. This could be related to how the skin is being set or updated in your simulation environment. One potential solution is to ensure that after setting the skin, you call skeletonAnimation.Update(0); to update the world transform values, as this is necessary for the changes to take effect properly. Additionally, make sure that the skin is correctly referenced and that there are no issues with the skin's setup in the Spine editor. If the problem persists, consider checking for any warnings in the Spine editor that might indicate an issue with the skin setup.
Fusion de 3 messages de Find a problem that only one skin isn't applied.
rmx That method should work, but instead of doing that, you can use setSlotsToSetupPose() to reset the slots to their setup pose values.
This is the more common approach, and note that calling this method together with the setSkin() is recommended in the general runtime guide: https://esotericsoftware.com/spine-runtime-skins#Skin-changes