Search Issue Tracker
Active
Votes
0
Found in
6000.4.0a2
Issue ID
UUM-121700
Regression
Yes
Editor glitches with artifacts/black spots when Editor Window is dragged to a secondary display configured to the left of the primary display
Reproduction steps:
1. Have at least two monitors for testing
2. Make sure the secondary display is set to the left of the primary display
3. Create and open any new project
4. Drag the Editor Window from the primary display to the secondary display
5. Observe the Editor
Expected result: Editor Window is rendered with no artifacts/black spots
Actual result: Parts of the Editor are completely black, and resizing does not work on those parts of the Editor or it causes significant glitching
Reproducible with: 6000.4.0a2
Not reproducible with: 6000.0.59f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Notes:
- Does not reproduce if the secondary monitor is to the right of the primary display
- Issue was reproduced with this display setup: Primary display - 3840x2400, 300% scaling, Secondary display - 2460x1440, 175% scaling
- If, after 4th step, the Editor layout is reset to Default, even more glitching can be observed (sometimes that glitching happens even without this step)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment