Search Issue Tracker
Fixed
Fixed in 2022.2.17f1, 2023.1.0b14, 2023.2.0a10
Votes
34
Found in
2022.2.4f1
2023.1.0b1
Issue ID
UUM-24656
Regression
Yes
[URP] The Scene View flickers when hovering over it with the cursor
Reproduction steps:
1. Open the attached “Spiders” project
2. Open the “Scenes/SampleScene” Scene in the Project window
3. Move your mouse over the Scene window
4. Observe the Scene View
Expected result: Scene View does not flicker
Actual result: Half of the Scene View (triangle shape) flickers
Reproducible with: 2022.2.4f1, 2023.1.0b1
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.3f1
Reproducible on: Ubuntu 20.04.5
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
drallcom3
Feb 01, 2023 02:39
Exactly this happens to me under Windows 11 with 2022.2.4f1. Something with the scene camera quad?
When opening 2022.2.3f1 projects in 2022.2.4f1 the scene view flickers heavily. When opening the project again in 2022.2.3f1 it disappears. Happens over multiple projects.
It's not easily to replicate, because it doesn't happen with new 2022.2.4f1 projects.
It's something about URP. Deleting URP makes the bug go away. Deleting all URP assets and creating new ones does not help. Weirdly using the URP assets from a new 2022.2.4f1 project in imported 2022.2.4f1 projects helps.
Creating a new 2022.2.3f1 and then opening it in 2022.2.4f1 does not cause the bug. Must be something older.