Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
939775
Regression
No
TextureImporterSettings.readable = true does not actually set the texture to allow for read/write
Steps to reproduce:
1. Download and open the attached project
2. Go to Window/Pixel Terrain/Import Texture and import a png file
3. Set it as a texture in the TerrainGenerator script
4. Press Analyze
Expected result: colors from texture are extracted and displayed in the inspector
Actual result: texture remains unreadable and an error is thrown
Reproduced on 5.5.4p2, 5.6.3f1, 2017.1.0p2, 2017.2.0b6, 2017.3.0a3
Notes:
-The texture appears to have the flag checked in the inspector until the Editor is restarted
-Setting the flag manually works as expected
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
Add comment