Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
1
Found in
2019.4.26f1
2020.3
2021.1
2021.1.6f1
2021.2
Issue ID
1340327
Regression
Yes
Canvas with Target Display set to Display 2 is not rendered when there is no Camera with Target Display set to Display 2
How to reproduce:
1. Open the attached "MultipleDisplay.zip" project
2. Open the "SampleScene" Scene
3. Go to File -> Build And Run
4. Observe the application on the second monitor
Expected result: UI Image is visible on the second monitor
Actual result: Black screen on the second monitor
Reproducible with: 2019.4.26f1, 2019.4.28f1, 2020.3.12f1, 2021.1.10f1, 2021.2.0a19
Not reproducible with: 2018.4.35f1, 2019.4.25f1
Comments (1)
-
PiotrekCiop
Jun 08, 2021 07:10
I can confirm this issue exists on 2019.4.27f1 too. Gave us quite the headache to figure it out.
We temporarily fixed it with a workaround: Add a dummy camera, set targetDisplay on it to target monitor, set cullingMask to 0 to make the camera render nothing.
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2021.2):
Fixed in: 2022.1.0a2
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b5
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.16f1