Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b12
Issue ID
1017582
Regression
No
Profiler.GetAllocatedMemoryForGraphicsDriver() always returns 0 in non-dev builds
Steps to reproduce:
1. Open "GetAllocatedMemoryForGraphicsDriver" project
2. Build for Windows standalone and run (development mode off)
-Profiler.GetAllocatedMemoryForGraphicsDriver() will return 0 (first line of output in the game view)
Expected result: for consistency, GetAllocatedMemoryForGraphicsDriver method should return valid value just like other Profiler methods do
Actual result: GetAllocatedMemoryForGraphicsDriver method always returns 0 in non-dev builds
Reproduced on: 2018.1.8f1, 2018.2.0f2, 2018.3.0a4
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