Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b11
2019.3.0f4
2020.1
Issue ID
1204973
Regression
Yes
[Profiler] Current frame data not shown after selecting previous frame for the second time.
-Frame marker is not moving to the position of the current frame for the second time.
-Also, current frame data is not shown.
Steps to repro:
1. Create a new project.
2. Window > Analysis > Profiler.
3. Enter Playmode.
4. Select any frame in the CPU section.
5. Click on the Current Frame tab.
6. Repeat step 4 & Step 5.
Actual Result:
Current frame is not showing on the second time.
Expected Result:
Current frame should be shown on the second time
Reproducible in:
2020.1.0a16, 2019.3.0f4 (e5c8d37da131), 2019.3.0b11.
Working Fine in:
2019.3.0b10.
Environment:
Occurring on Windows 10 & Mac.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [2023.2] HDRP Asset Settings Helper throws a NullReferenceException
- [URP] SubmitRenderRequest with NativeRenderPass + Upscaling doesn't work
- “ArgumentOutOfRangeException” error appears when inserting a double character if using “SetValueWithoutNotify” on UI Toolkit’s TextField
- Particle System emission delays between particle generations when playing the simulation
- EditorUtility.DisplayDialog is not shown when Input.GetMouseButtonDown is called a second time
Add comment