Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.34f1
6000.0.7f1
7000.0.0a1
Issue ID
UUM-74936
Regression
No
ChangeDisplayAsync Fails on Mixed Resolution and Orientation Monitors
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Connect a 4k monitor and another with a different resolution and a Portrait mode
4. Build and Run
5. In Player, press “F3“
6. Select a different display for the Display option
Expected result: The Player is rendered on another monitor
Actual result: The Player fails to change the target display
Reproducible with: 2022.3.34f1, 6000.0.7f1
Could not test with: 2021.3.39f1 (Assets\DisplayHelper-main\Runtime\Helper.cs(83,85): error CS1061: 'Resolution' does not contain a definition for 'refreshRateRatio' and no accessible extension method 'refreshRateRatio' accepting a first argument of type 'Resolution' could be found)
Reproducible on:
Windows 10 Enterprise 21H2 (LG C24G1 Portrait and HP Z27k G3 Landscape)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- If both monitors are the same, not reproducible
- If both monitors are under 4k but have different sizes, not reproducible
- If monitors have different resolutions and one of them is 4k, reproducible
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.