Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.3.18f1
2020.3.28f1
2021.2
2021.3
2022.1.0a8
2022.2
Issue ID
1404047
Regression
Yes
File could not be read error is thrown when a 16 bit .tif file is present in the project
Reproduction steps:
1. Open users attached project
2. Observe the Console window
Expected result: No errors are thrown in the console
Actual result: "File could not be read" error is thrown
Reproducible with: 2020.3.18f1, 2020.3.32f1, 2021.2.19f1, 2021.3.1f1, 2022.1.0a8, 2022.1.0b14, 2022.2.0a10
Not reproducible with: 2019.4.38f1, 2020.3.17f1, 2022.1.0a1, 2022.1.0a7
Note: Try re-extracting the project if the error doesn't appear
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a16