Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.13f1
2020.1
2020.2
2021.1
Issue ID
1293004
Regression
Yes
Profiler window flickers excessively when profiling a built player with VSync disabled
How to reproduce:
1. Create a new Unity project
2. Open the Project Settings > Quality window
3. Set VSync Count to 'Don't count'
4. Open the build settings and check the development build checkbox
5. Build and run the player
6. Connect Unity profiler to the player
7. Select one of the modules(e.g. Live CPU usage or Audio simple) and use the scroll wheel inside the Profiler window
Expected result: the profiler is smooth
Actual result: the profiler is flickering constantly
Reproducible with: 2019.4.15f1, 2020.1.15f1, 2020.2.0b11, 2020.2.0a5
Not reproducible with: 2018.4.29f1
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
- “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
Resolution Note (2021.1.X):
The amount of frames shown in the profiler should be set to a higher number if this is happening to allow the frame to remain available to show the data for it.