Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4.15f1
Issue ID
1297258
Regression
No
[Encoding/compression] Lightmap Encoding changes cause unexpected TextureImporter state on Reflection Probes (iOS)
Repro:
1) Be sure to have iOS support installed.
2) Create new project and set build target to iOS.
3) Generate standard reflection probe by pressing "Generate Lighting" in Lighting window.
4) With the generated reflection probe visible in Inspector, change the Lightmap Encoding.
5) Observe the unexpected message "Not yet compressed" in the bottom of TextureImporter.
Expected: You can change Lightmap Encoding without ending up in the "Not yet compressed" state.
Actual: You end up in the "Not yet compressed" state.
The repro was done using 2019.4.15f1 on MacOS.
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
Add comment