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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment