Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-120275
Regression
No
Profiler Current Frame indicator not draggable when dragging for the first time on a different module
How to reproduce:
1. Create and open a new project
2. Open the Profiler window
3. Switch the Profiler to from Play Mode to Edit Mode
4. Click the record button “Record profiling information (f9)” to start recording
5. Wait for two seconds
6. Click the record button “Record profiling information (f9)” to stop recording
7. Click on the CPU Usage module graph
8. Move the mouse to the filled Rendering module graph
9. Start holding down the left mouse button
10. Move the mouse to the filled CPU Usage module graph
11. Release the left mouse button
12. Observe the Current Frame indicator
Expected result: Current Frame indicator jumps to the current mouse location
Actual result: Current Frame indicator does not jump to the current mouse location
Reproducible with: 2020.2.0b3, 2021.1.0a10, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Not reproducible with: 2020.3.43f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment