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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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.