Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
Issue ID
UUM-65787
Regression
No
[Android] Some monitors display only 1/4 of the Player when built with UnityPlayer.displaychanged() and Camera.targetDisplay() or Camera.SetTargetBuffers() for Android with multiple displays
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Build and Run on the RK3588 device which has 3 HDMI outputs and is connected to displays with 800x1280, 1920x1080, and 3840x2160 resolutions
5. Observe the Player across all monitors
Expected result: All monitors display the Player fully
Actual result: Some monitors display only 1/4 of the Player
Reproducible with: 2021.3.34f1c1 (User reported)
Reproducible on:
RK3588 (User reported)
Testing environment: Windows 10 (10.0.19045) 64bit (User reported)
Not reproducible on: No other environment tested
Notes:
- CQA couldn’t test the issue locally
- The Player can find 4 display devices, but one active is false and the resolution is 64*64
- When using Camera.targetDisplay() 2nd monitor only displays 1/4 of the Player
- When using Camera.SetTargetBuffers() 3rd monitor displays 1/4 of the Player
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
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.