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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment