Search Issue Tracker
Fixed in 4.0.2
Fixed in 2.1.6, 3.1.6
Votes
1
Found in [Package]
2.1.4
Issue ID
1266986
Regression
Yes
Importing .psb files with vector layers imports textures incorrectly
How to reproduce:
1. Open the attached project "psbBug.zip"
2. Import the attached .psb file "Rompdeor_char2.psb"
3. Drag the imported .psb file into the Scene View and observe it
Expected result: the .psb file imports correctly (see correct.PNG)
Actual result: the .psb file imports textures incorrectly (see incorrect.PNG)
Reproducible with: 2019.3.13f1, 2019.4.8f1 (2.1.4), 2020.1.2f1 (3.1.4), 2020.2.0a20 (4.0.0)
Not reproducible with: 2018.4.26f1 (1.0.0-preview.4), 2019.3.13f1 (2.1.3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 4.0.2):
Fixed in Package Version: 2D PSD Importer 4.0.2
Resolution Note (fix version 3.1.6):
Fixed by Package: 2D Psd Importer 3.1.6
Resolution Note (fix version 2.1.6):
Fixed by Unity Package: 2D PSD Importer 2.1.6