Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b4
Issue ID
909569
Regression
No
'Could not create texture' error is shown after importing texture
Steps to repro:
1. Open attached project;
2. In the Project folder multiselect four Rock texture files by using Shift-click;
3. Right mouse and click 'Reimport'.
Expected result:
Texture is reimported without errors.
Actual result:
Errors:
'Could not create texture from Assets/Rock_AO.png: File could not be read'
are thrown. See attached screenshot.
Notes:
- Reproducible in 2017.1.0b4, 5.6.0p4, 5.5.2p1;
- Reproducible on OSX 10.12.3 and Windows 10;
- Reproducible only for these specific texture files, not reproducible for other textures;
- There is no valid workaround for this issue. Tried lots of things, like reimporting, deleting/restoring, etc.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment