Search Issue Tracker
Not Reproducible
Votes
0
Found in
Issue ID
1010507
Regression
No
Light probe visualization carries a huge cost even when not rendering due to disabled gizmo settings
Light probe visualization carries a huge cost even when not rendering due to disabled gizmo settings, when the scene has tens of thousands of light probes having light probe visualization settings enabled comes with a 100-200 ms cost on a large i7,even if lightprobe gizmo drawing is disabled, this becomes kind of a trap as it is easy to forget you enabled that mode in the lighting panel and will continue to pay the cost for something that is not even rendered.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment