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
Comments (2)
-
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
- 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
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a6