Search Issue Tracker
Fixed in 2022.2.X
Votes
1
Found in
2019.4.31f1
2020.3.19f1
2020.3.26f1
2021.2
2022.1
2022.2
Issue ID
1397028
Regression
Yes
Error "File could not be read" when importing BMP assets with specific properties
Reproduction steps:
1. Create and Open a new Project
2. Import the attached image example.bmp
Expected result: .bmp asset is imported
Actual result: "File could not be read" error is thrown in the Console Window
Reproducible with: 2019.4.31f1, 2019.4.34f1, 2020.3.19f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b4, 2022.2.0a3
Not reproducible with: 2019.4.30f, 2020.3.0f1, 2020.3.18f1
Notes:
Importing 16, 24 bit .bmp with "Do not write color space information" checked when exporting, imports to the project
Importing 32 bit .bmp with "Do not write color space information" checked when exporting, does not import to the project
Importing 16, 24, 32 bit .bmp with "Do not write color space information" unchecked when exporting, doesn't import
-
snarlynarwhal
Aug 16, 2022 21:17
I am still encountering this issue on 2020.3.26f1 and also need it fixed for Nintendo Switch.
-
Liderangel
Feb 10, 2022 04:06
Would be much appreciated a fix due to the Nintendo Switch platform asking for a .bmp icon to build
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
- [HDRP] 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
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a6