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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment