Hi!
Trying to work with the 2D package, PSD Importer in particular.
The importer refuses to import the original layout of the psb file.
Notice my Layer Management Tab:
In comparison with the Skinning Editor hierarchy:
In the beggining only some of the layers were missing, but after trying to solve it by choosing different Layer Mappings I lost a whole group of layers.
In addition some layers are completely misaligned (notice the hair layer inheriting the jacket’s shape as a weird mask):
The psb file in photoshop renders correctly and there are no effects whatsoever on any layer.
It’s really hard to work with the 2D package with bugs all over the place. Is there anything I’m missing?
My import settings are:
1 Like
Additional info: All errors were introduced after adding, removing layers to the .psb file. Saving from photoshop as a new file properly imports all the sprites, but recreating all the mesh data, reassigning all the sprites in the sprite librarys would be a really tedious task…
Is regularly uptating the source psb something that’s not supported?
Bump?
Does the ID based layer mapping use some custom ID generated in photoshop or is the ID just the index of the layer? The mixup may have happened because the order of the layer changed inside of photoshop, but the imported asset still referenced the old ID?
In this case going for layer mapping by name maybe a better idea (case sensitive especially).
Hey kind of a long shot, but I’m experiencing something similar. Do your affected layers happen to have masks in photoshop? Did you ever solve the problem?
Hi!
When we updated our Unty version to 2022.3.46f1 a lot of the bugs in the 2D package and PSD package were gone.
We also made sure to never ever use the same name of 2 different layers in photoshop and reimported all psb files.
Not sure what exactly solved the issue, but we haven’t experienced it since.
thanks! I think it’s a different bug than mine then, because I still have it on 2022.3.46. I saw it was actually solved on 2023.1.22, but then resurfaced for some reason in unity 6. so I’ll probably jump to the 2023 even if it isn’t LTS.
Are you guys staying with 2022.3.46 even if it’s flagged with the security issue?
Yea, some of these packages just don’t get the attention they deserve. This post was written more than a year ago and I haven’t received any official response.
Of course, we’re updating to the latest version.
