Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
2
Found in
2019.3.0a10
2019.3.0f3
2020.1
Issue ID
1209185
Regression
Yes
[D3D11] Game view Statistics tab reports false values when using SRP
How to reproduce:
1. Create a new URP Template project
2. Open the Statistics tab in the Game window
3. Observe the number of triangles and vertices currently in the Scene
4. Change the Game window size or add additional objects in the Scene
5. Observe the Statistics tab again
Expected behavior: Game window stats are updated and reflect the current rendering data (Track_1209185_V2)
Actual behavior: The stats tab is not responding or reporting false values (Track_1209185_V1)
Reproducible with: 2019.3.0a10, 2019.3.0f5, 2020.1.0a19
Not reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0a9
Could not test with: 2017.4.36f1(No Package Manager)
Reproducible with package versions: 7.0.0, 8.0.0
Not reproducible with package versions: 4.1.0, 6.9.2
Notes:
1. Reproducible with URP and HDRP
2. When HDRP is used Stats report 0 vertices and triangles (Screenshot_1209185_V1)
3. Only reproducible with D3D11. APIs tested - D3D11, D3D12, Vulkan and Metal
4. SRP 7.0.0 was introduced in 2019.3.0a10
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a20
Resolution Note (fix version 2020.1):
Fixed in - 2020.1.1f1
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.29f1