Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.5.0a1
Issue ID
771876
Regression
No
[ReflectionProbe] Baking custom reflection light probes overwrites the user-created *.exr cubemap
Baking custom reflection light probes when an .exr file (Texture type: cubemap or HDRI) is assigned as the custom cubemap overwrites the user's file.
Repro steps:
1. Open Test1 scene from attached project.
2. Select Reflection Probe from Hierarchy.
3. Observe the currently selected custom cubemap.
3. Click "Bake".
4. Observe how the cubstom cubemap got overwritten.
Expected outcome: to not overwrite user texture or give a warning that assigned cubemap will be overwritten when an .exr texture file is used.
Notes:
- a cube map of any other texture format than *.exr prompts the user to save new cubemap.
- not a regression, testes as far back as 5.3.1f1.
- Appears to be typical light probe behavior, however since Version 5.5.0a1 (5a6d256ca545) graphics/staging branch more emphasis is added on .exr and .hdr textures, making this potentially a more common issue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
Add comment