Search Issue Tracker
Fixed in 5.3.0
Votes
1
Found in
5.1.2p3
Issue ID
721083
Regression
No
[Windows] Windows player issues on dual monitor setup
To reproduce:
1. Build and run project
2. Press full screen button
3. Press No full screen button
4. Notice that the application goes to the middle position between the monitors.
5. Move the window to secondary display
6. Press full screen button.
7. The application runs in full screen mode on the primary display
On Windows, if you run the fullscreen mode, it's always running on the main display. If you switch to windowed mode, the application goes to the middle position between the two screens. If you move the windowed application to secondary screen at change to full screen it will run on the primary display.
Resolved (Fixed):
Switching from windowed to fullscreen mode will fullscreen player in the same monitor where it was in the windowed mode now.
Switching from fullscreen to windowed mode will still center the window between two monitors and that is an expected behavior. When centering the windowed player we check if player window size + windows borders are less than the monitor resolution. If that's the case, then we center the window in the same monitor where the fullscreen app was. However if player size + borders are bigger than the monitor resolution (which happens when the player is rendered at native monitor resolution in fullscreen) we center the window in the middle of virtual screen. As a workaround you could lower resolution before switching from fullscreen to windowed mode.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment