Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
6000.0.35f1
6000.1.0b3
6000.2.0a1
Issue ID
UUM-95538
Regression
No
Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
Reproduction steps:
1. Make sure at least two displays are available for testing
2. Open the attached “IN-90909.zip” project
3. Go to File > Build Profiles and make sure only “New Scene” is in the Scene List
4. Build and Run the Project (File > Build and Run)
5. Observe the built Player on both of the displays
Expected result: Both displays are rendering results
Actual result: All cameras render to Display 0 and other displays render black
Reproducible with: 6000.0.35f1, 6000.1.0b3, 6000.2.0a1
Couldn’t test with: 2022.3.56f1 (Could not downgrade)
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- This issue does not occur with DX11 or Vulkan. When the graphics API is switched to DX11, cameras render correctly to their assigned displays
- Debug logs confirm that displays are activated, and cameras are correctly assigned
- Could not reproduce on a new project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Add comment