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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment