Search Issue Tracker
Fixed
Fixed in 6000.2.0a7
Votes
0
Found in
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.0a7
Issue ID
UUM-91905
Regression
No
Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
Reproduction steps:
1. Make sure you have HDR enabled (“Display settings → Use HDR → On“ on Windows)
2. Open the attached “repro_IN-87676“ project
3. Make sure that “Direct3D12” is set as the default graphics API (“Edit → Project Settings… → Player → Other Settings → Rendering → Graphics API for Windows“)
4. Open the "Assets/OutdoorsScene.unity" Scene
5. Enter the Play Mode
6. Press the "Space" button on your keyboard
7. Change the resolution to your preferred one with the 'E' button
8. Observe the Game view
Expected result: Each of the 4 split screens displays a spinning cube
Actual result: Only 1 (the top-left) split screen is displaying a spinning cube, the other three are either showing a frozen image or a black background
Reproducible with: 2022.1.0a16, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Not reproducible with: 2021.3.47f1, 2022.1.0a15
Reproducible on: Windows 10 (22H2), Windows 11 (23H2) (reporter’s environment)
Not reproducible on: No other environments tested
Notes:
- Not reproducible with DirectX11
- Not reproducible with Vulkan
- Not reproducible in Player while testing, but the reporter mentioned that they managed to reproduce the issue in Player on some of their devices
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
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
There are no fixes planned for this Bug