Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a3
2019.3.0b10
Issue ID
1197220
Regression
Yes
[Profiler] Frame key deactivates on resuming editor on selecting Profiler Modules values
Frame key deactivates on resuming editor on selecting Profiler Modules values
Steps to Reproduce:
1. Create a new Project
2. Open Window > Analysis > Profiler
3. Change Mode to Playmode and run the Editor
4. Select CPU Usage value in the Editor Mode
5. Resume Editor
Expected Result:
- Frame key appears with related data on the left and right side of the key
- On resuming the Editor, Frame Key moves according to the frames
Actual Result:
Frame Key moves according to the frame but deactivates in next frame and activates in next to next frame
Reproducible on: 2020.1.0a12, 2019.3.0b10, 2019.3.0b5, 2019.3.0a3
Working fine on: 2019.3.0a1, 2019.2.8f1, 2019.1.12f1
Note: This issue is occurring with AMD Radeon R9 200 Series Graphics card
Environment: Windows 10 only
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment