Search Issue Tracker
Fixed
Fixed in 6000.4.0a4
Votes
0
Found in
6000.4.0a2
Issue ID
UUM-121700
Regression
Yes
[WinEditor] MainWindow fails to paint correctly when dragged across multiple displays with different DPI scales
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment