Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a9
2019.2.0a1
2019.3.0a1
2019.3.0a8
Issue ID
1169890
Regression
No
GameView.Paint is renamed to another window's .Paint activity when the other window is docked with Game View window
How to reproduce:
1. Create a new project
2. Go to Window > Layouts and select Default
3. Enter Play Mode
4. Open the Profiler, select "Editor" as target (or enable Profile Editor in older versions), select the Hierarchy view of the "CPU Usage" Profiler Module
5. In the Profiler, enable Record
6. In the Hierarchy view go to EditorLoop > ApplicationTickTimer > UpdateScene > UpdateSceneIfNeeded > UpdateScene > GUIView.RepaintAllPlayerLoopController
Expected result: The GUIView.RepaintAllPlayerLoopController has an activity named GameView.Paint
Actual result: The GUIView.RepaintAllPlayerLoopController has and activity named SceneView.Paint
Reproducible with: 2019.1.11f1, 2019.2.0b10, 2019.3.0a10
Notes:
- It is required for the layout to change for this problem to occur
- It seems that only the name is registered incorrectly as the further registered activity is related to Game View window
- The name is registered incorrectly even if the window docked with GameView window is deleted
- GUIView.RepaintAllPlayerLoopController became available from 2019.1.0a10. Before that, the Activity was called GUIView RepaintAll
- Until version 2019.1.0a8 GUIView RepaintAll did not contain .Paint activities
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
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
- VFX Graph link contrasts fail WCAG guidelines
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a12