FeedMyData

Hi,

Today I was trying to understand why some freshly reexported spine assets in my unity project started to have alliasing.
After researching, I found out it was coming from the imported spine texture.

After thinking it came from the latest Spine version, I realized that I changed one parameter recently on my texture packing.
Instead of asking to create two textures, one with scale 1, and one with scale 0.8, I asked Spine to only create a 0.8.
I thought I would spar some processor time and disk space.

But it seems that by doing so, when exporting the texture only at 0.8, spine is having issues.
However when I check the 0.8 texture when simultaneously exported with a scale 1 texture, it looks fine.

Repro :
1. Open a spine project (v4.40)
2. Export the texture with the following settings.
Screenshot_1.png

3. Change the pack settings to only export at scale 0.8 (here come the aliasing)
4. Compare the previous 0.8 export with the new 0.8 export

Here is a comparison of the two 0.8 texture (Right Repro step 2, left Repro step 3)
Screenshot_2.png
Vous ne pouvez pas consulter les fichiers insérés à ce message.
Avatar de l’utilisateur
FeedMyData
  • Messages: 29

Misaki

Hi,

Sorry for the trouble, the 4.0.40 accidentally changed the default texture-resampling setting to Near(Nearest neighbor).
resample-settings.jpg


We’ve fixed it in 4.0.41 and it has been released. Please update your Spine editor to 4.0.41. If you ran 4.0.40, you may still need to change it from Nearest to Bicubic.
Vous ne pouvez pas consulter les fichiers insérés à ce message.
Avatar de l’utilisateur
Misaki

Misaki
  • Messages: 238

FeedMyData

I did not notice the two parameters were different. Well spotted thanks!
Avatar de l’utilisateur
FeedMyData
  • Messages: 29


Revenir vers Bugs