Search Issue Tracker
Active
Votes
11
Found in
2022.2.5f1
Issue ID
UUM-25995
Regression
Yes
[2022.2] “targetDisplay” doesn’t change the camera’s “Target Display” setting when called from the script
How to reproduce:
1. Open the attached “TargetDisplay.zip” project
2. Open the “SampleScene” Scene (Assets > Scenes > SampleScene)
3. Enter Play Mode and observe “Camera1” and “Camera2” GameObjects “Target Display” setting
Expected result: Cameras' “Target Display” settings are “Display 2” and “Display 3”
Actual result: Cameras “Target Display” setting is “Display 1”
Reproducible with: 2022.2.1f1, 2022.2.5f1
Not reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.2.0f1, 2023.1.0a1, 2023.1.0b2
Reproduced on: macOS 12.4 (Intel)
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
- RegisterValueChangeCallback is not called when changing the PropertyField value
- The Properties option is missing when pressing RMB on the PropertyField
- [Android] forward+ lighting glitch when built on Xiaomi Mi 10
- Lens Flare occlusion effect doesn't work when the Camera GameObject is behind obstacles
- Texture Importer: Swaps red and blue channels
callumroseFC
Mar 16, 2023 15:50
I can verify that I've seen this bug too in 2022.2.10f1 and 2022.2.11f1 on Windows. CASE IN-35493