Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.33f1
6000.1.0a10
6000.3.0a1
6000.4.0a1
Issue ID
UUM-91585
Regression
No
[HDRP] Missing sky contribution when HDRP lighting is baked in batchmode
How to reproduce:
1. Extract the “IN-91330_HDRP Baking Project.zip“ project
2. In the Command Line write “<UNITY.EXE PATH> -quit -batchmode -projectPath "<PROJECT PATH>" -executeMethod AutoBaker.StartBake“
3. Open the project normally after the Editor fully closes in the background
4. Open the “OutdoorsScene“ and observe the Game view
5. Open the Lighting window in Window > Rendering > Lighting
6. Generate the Lighting with the “Generate Lighting“ button at the bottom of the Lighting window
7. Observe the Game view after the Lighting finishes generating
Expected result: The lighting in the Game view does not change after running BakeAsync
Actual result: The lighting in the Game view becomes brighter than after running BakeAsync
Reproducible in: 6000.0.18f1, 6000.0.33f1, 6000.1.0a10
Not reproducible in: 2021.3.47f1, 2022.3.55f1, 6000.0.17f1
Not a regression, the issue was discussed in 2022: [https://unity.slack.com/archives/C0108P9UH6H/p1645626215653739?thread_ts=1645564453.159699&cid=C0108P9UH6H]
Reproduced on:
- Windows 11 Pro (23H2)
- macOS Apple Silicon
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.