koobas.hobune.stream
Could building on Windows 10 corrupt sprites?
Hello guys,
I recently changed my working laptop and moved from Windows 7 to Windows 10 pro. I also moved from Unity 5.4.1 to Unity 5.5.1.
I am experiencing quite some problems in the build. Our game is all sprite based (we have quite some large spritesheets, and lots of UI sprites), all of them kept in POT format, but some as large as 4k and 8k.
On the old laptop i had no problem, in the new one instead (I also tried to roll back on the new one with the 5.4.1 version to make sure it was not a version issue, i get several sprites looking corrupted in the build (in the editor they have no problem). You see below that some of them disappear, create some weird issues with colors (i noticed some even having some pieces of other sprites superposed, as the image attached, where instead of the tower shadow out of the right spritesheet, i get the right sprite shape, but showing some different scales out of the dogs animation sheet)
Any Idea on what might be the cause? I tried with a single sprite, copying it from the game folder, cancelling it from the project, and reimporting it, and it worked, but doing that for all the non working ones (specially the animation sheets) is a killer that i would try to avoid as it would take days to locate then and change them. Specially because in the editor everything works fine.
Cheers, H
I doubt it's related to Windows 10; it sounds much more like a result of the upgrade to Unity 5.5.
Specifically, from your description of the editor/playmode difference, and the wrong textures being used on sprites, I'd say this relates to your sprite atlases needing to be recreated. We experienced a somewhat similar issue - it seems that the atlas packing policy is not entirely deterministic between different Unity versions, and it's easy for the sprite metadata to become desynchronised with the atlas texture itself when upgrading.
Have you tried removing and rebuilding the AtlasCache library folder?
Hi @tanoshimi ,yep, I tried to completely clean the library folder, and let it recreate it in the project completely, but nothing changed. What made me thing it might be related to Windows 10 is that i took the original folder from the old laptop and Unity 5.4.1 on this computer, installed Unity 5.4.1 and then built, and I had exactly the same issue, that I don't get ins$$anonymous$$d on the old laptop.
