Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.49f1
6000.1.2f1
6000.2.0b1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-105061
Regression
No
[HDRP] Scene corrupts when baking Reflection Probe with custom TextureImporter preset added to Texture Importer default
How to reproduce:
1. Open attached “IN-98470” project
2. Open “OutdoorScene” from the Project tab
3. Select “TextureImporter” preset asset in the Project tab
4. At the top of the Inspector, click the "Add to Texture Importer default" button
5. In the Hierarchy select the “Reflection Probe” GameObject
6. In the Inspector click the “Bake” button at the bottom of the “Reflection Probe” component
7. Observe the Scene view
Expected result: Scene is not corrupted
Actual result: Scene is corrupted
Reproducible with: 6000.0.11f1, 6000.0.49f1, 6000.1.2f1, 6000.2.0b1
Not reproducible with: 2022.3.61f1, 6000.0.10f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Does not affect URP projects
- Errors in the Console are expected, as the generated texture gets converted to incorrect format, when baking the reflection probe (Present in both URP and HDRP projects)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.