Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-26101
Regression
No
Total Bake Time is always shown as 0 after precomputing realtime GI
Jira twin of: [https://fogbugz.unity3d.com/f/cases/1355229/]
Steps to repro:
- Open the attached project ([^RealtimeGIPrecomputeNoTotalTime.zip])
- Open SampleScene scene;
- In the Lighting window (Window>Rendering>Lighting) press Generate Lighting button;
- Wait until the scene's lighting finishes baking;
- Observe the bottom section of the Lighting window.
Expected result:
- Total Bake Time field shows actual time spent on Precomputing Realtime GI. See attached screenshot.
Actual result:
- Total Bake Time is shown as "0:00:00".
Notes:
- Reproducible in 2022.1.0a4, 2020.3.15f2, 2019.4.29f1;
- Reproducible on Windows;
- Reproducible only with Realtime GI, not reproducible with Baked GI.
- If it's not possible to explicitly show the time spent on precomputing realtime GI, then it would make sense to just remove that field in this particular case.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.