Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.5f1
2022.1.8f1
2022.2.0a18
2023.1.0a2
2023.2.0a1
Issue ID
UUM-7775
Regression
Yes
Deselected Game View is rendered incorrectly when resizing Game View window in two Game View window setup
Reproduction steps:
1. Open the attached project
2. Click the right mouse button on the “Game” tab
3. Click “Add Tab” > “Game”
4. Drag the new “Game View” window to the side of the currently opened “Game View” window
5. Resize the “Game View” window
Expected result: “Game View” is rendered correctly
Actual result: Black area is shown in the “Game View” that is deselected (see attached video)
Reproducible with: 2021.3.2f1, 2021.3.5f1, 2022.1.8f1, 2022.2.0a18, 2023.1.0a2
Not reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.1f1
Reproducible on: Windows Pro 20H2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The core of this issue is about Camera. As there is a single camera and a single target screen for camera, the camera uses the active screen and we see black rectangles on non active views if they are larger than the active screen. We abandoned the fix since it creates significant complications for the multi display support and regression risk which are not justified considering the low UP of the bug.
Resolution Note (2023.2.X):
The core of this issue is about Camera. As there is a single camera and a single target screen for camera, the camera uses the active screen and we see black rectangles on non active views if they are larger than the active screen. We abandoned the fix since it creates significant complications for the multi display support and regression risk which are not justified considering the low UP of the bug.