Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.3
2020.3.0f1
2021.1
2021.2
Issue ID
1321964
Regression
No
[Profiler] ProfilerRecorder gives invalid values in standalone Build
Steps to reproduce:
1. Download and open project "ProfilerRecorderBugTest.zip"
2. Make sure that "ProfilerScene" is open
3. Enter Play Mode
4. Notice the ProfilerRecorder values in Game View
5. Exit Play Mode
6. Go to File -> Build Settings and ensure “Scenes/ProfilerScene” is set for “Scenes in Build”, if not hit “Add Open Scenes”
7. Click “Build and Run”
8. Notice the ProfilerRecorder values in the Build
Expected Result: All values displayed by the ProfilerRecorder are greater than 0 MB
Actual Result: ProfilerRecorder displays “GPU Memory Usage”and “GPU Reserved Memory” as 0 MB
Reproducible with: 2020.3.2f1, 2021.1.0f1, 2021.2.0a10
Could not test with: 2018.4.33f1, 2019.4.23f1 (ProfilerRecorder not available)
Notes:
Issue was reproducible on MacOS Catalina(10.15.7) and on Windows 10
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 2021.2):
The issue was fixed in the documentation (https://docs.unity3d.com/Manual/ProfilerMemory.html)