Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.5.0b4
Issue ID
594652
Regression
No
DX11 standalone on dual screen always runs on the same screen
To reproduce:
You must be using a dual screen setup
1. Create a new project
2. Enable dx11
3. Build & run windows standalone
4. In the resolution dialog, set it to fullscreen. Note at what monitor the executable runs
5. Open the display setup on your OS. Switch the main display to the other screen
6. Run the executable again - the dialog appears on the correct (main) screen, but the standalone still runs on the first one (the secondary screen)
Expected: everything runs on the main screen only
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Add comment