Search Issue Tracker
Fixed in 2017.1.0f3
Votes
0
Found in
2017.1.0b3
Issue ID
908211
Regression
Yes
[Texture] 16-bit greyscale PSD cant be read
16-bit greyscale PSD cant be read
2. How we can reproduce it using the example you attached
1) Open project
2) Reimport Rocks_H.psd
3) See error
"Could not create texture from Assets/Rocks_H.PSD: File could not be read"
Reproducible in 2017.1b3
Not reproducible in 5.6.0f3
Comments (1)
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
Arcanor
Jul 28, 2017 11:00
I am still seeing this problem in unity 2017.1.0f3. I can reproduce with a fresh project, and import the latest version (1.3.7) of Opsive's "Third Person Controller" asset package. The package includes 5x 16-bit grayscale PSD files. For each of them I get an error like this:
Could not create texture from Assets/Third Person Controller/Demos/Third Person Shooter/Textures/Warehouse/Tileable/Floor1_ambient_occlusion.psd: File could not be read