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
- WebGL build dependencies are not refreshed until the Editor is restarted
- “Audio Random Container” allows adding unlimited number in “Audio Clips” numeric field, causing Editor to freeze
- In Deferred rendering path, mixed lights don't render when enabling "Use Rendering Layers" in the Decal renderer feature
- [Windows] Special characters in file names are sorted to the end of the alphabet in the Project window
- Information box icons are not contained within the information box bounds in Render Pipeline Converter window
Add comment