Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0f3
Issue ID
943676
Regression
No
Reflection Probes incur cost (per renderer) regardless of proximity to existing renderers, or static flags on any elements
Reproduction steps:
1. Open project attached (ReflectionProbePrefTest.zip).
2. Open Profiler
3. Start Scene
4. View DrawOpaque in profiler
5. Select All Reflection Probes
6. Turn them on and off, observing the change.
Expected result: The reflection probes should not (or by small amount) affect the amount of time it takes to do "DrawOpaque".
Actual result: DrawOpaque takes about 0.25 ms longer (depending on PC).
Reproduced on: 5.5.4p4, 5.6.3p2, 2017.1.0p5, 2017.3.0a6.
Notes: Reflection probes incur a draw cost based on the # of renders in a scene, regardless of whether probe or renderers are static, and regardless of whether the probe is touching anything.
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