Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
8.2.0
Issue ID
1263331
Regression
No
[HDRP] Overexposed previews if baked lighting data is present
Version tested 2020.1.0b16 + 8.1.0/8.2.0
Steps to reproduce:
1) Create new HDRP template
2) Check prefab or mesh previews. Notice they are over exposed.
3) Remove baked light data
4) Check previews again (reimport if needed), they will look correctly.
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
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Resolution Note:
Unfortunately there isn't much we can do about this issue. The lightmaps for these objects contain high HDR values intentionnaly. What we need is the preview to have an exposure control to visualize this kind of objects so this will be fixed once we have that.