Search Issue Tracker


Fixed in 2022.3.0f1



Found in


Issue ID




[2022.2] “targetDisplay” doesn’t change the camera’s “Target Display” setting when called from the script



How to reproduce:
1. Open the attached “” 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)

  1. Resolution Note (fix version 2022.3.0f1):

    Fixed in: 2022.3.0f1

Comments (6)

  1. AlbinZosimusJulius

    May 19, 2023 14:00

    This regression really is a blocker for applications that control multiple displays. As the camera components `m_TargetDisplay` field is only accessible from the native code or the serializer, it is impossible from the runtime to change this property.

    The only workaround I found so far is to actually instantiating a new camera component for every display change. Super ugly...

  2. Teatoon

    May 15, 2023 10:13

    Tested in 2022.2.19f1, problem is still there.

  3. Teatoon

    Apr 28, 2023 21:43

    I confirm that this is not fixed in 2022.2.16f1

  4. paljoci

    Apr 28, 2023 13:33

    This issue is still not fixed in 2022.2.17f1

  5. naonaonaoue

    Apr 21, 2023 11:15

    This issue is still not fixed in 2022.2.16f1.
    Do your best!!

  6. 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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.