Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2019.1.X
Votes
0
Found in
2017.2.0b7
2017.3.0a4
2018.1.0f2
Issue ID
1040726
Regression
Yes
Primary screen window size turns to native when using more than one display
How to reproduce:
1. Open the attached project
2. Open DoubleDisplay.cs script
3. For methods Display.displays[0].SetParams and Display.displays[1].Activate, change window size parameters to 480x480
4. Build and Run the project
Expected result: When the game is launched, in both displays window sizes are like the ones that are set in the DoubleDisplay.cs script.
Actual result: The primary display window size turns to native. (Second screen has expected behavior.)
Reproducible with - 2017.1.0p5, 2017.1.4p1, 2017.2.0b7, 2017.2.3p1, 2017.3.0a4, 2017.4.5f1, 2018.1.5f1, 2018.2.0b8, 2018.3.0a2
Not reproduced with - 2017.1.0p4, 2017.2.0b6, 2017.3.0a3
Notes:
- After regression, when using only one display, the window size is the same as Screen Resolution that is selected when launching the build (instead of the one that is set by Display.displays[0].SetParams in the script).
-
createaname6
May 05, 2021 20:51
GTA 5 BY GAMES SCIENTIST. PS7z
Size: 375.99MB (394258320B)
MD5: 6bae08ebf5d2651226e5d24e80161b15
Type: 7z / LZMA:20 7zAES
Solid: GTA5 iJ
File count: 2143
Content size: 389.56MB (408488279B)
Compression ratio: 96% -
catfink
Mar 12, 2019 12:59
My customers are reporting that it is not fixed at all - so I don't think the fix works
-
Huacanacha
Mar 01, 2019 22:45
This fix seems likely to have introduced a new issue: the secondary display resolution is now locked to the primary display resolution in Windows 10 (not Win7), leaving black bars when second display is higher native res than primary.
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2018.3):
Fixed in 2019.2.0a5
Backported to 2017.4.36f1, 2018.3.8f1, 2019.1.0b4