Search Issue Tracker

Fixed in 5.2.2



Found in


Issue ID




[2D] Screen position out of view frustum errors

Scene/Game View


Open scene Game in attached project. Reimport all assets in the Project and notice 8 errors about "Screen position out of view frustum" (seem to come from Handles-related code).

Comments (58)

  1. 0e182adb5c14f5bcb7694ad8a498565f?d=mm


    Oct 28, 2015 19:10

    Still get the same error in 5.2.2f1. Issue not yet resolved.

  2. F20c8b0c25e99bdd733446caa3123e58?d=mm


    Oct 26, 2015 04:13

    Just started happening to me for the first time, once I migrated from 4.6 to 5.2.2f1.

    "Screen position out of view frustum (screen pos 0.000000, 0.000000, 1000.000000) (Camera rect 0 0 0 0)

  3. 53aee60683b1af13943c27347cf03c3f?d=mm


    Oct 25, 2015 13:18

    Not fixed.

  4. A86346d54a12afe4e04109c22de6b116?d=mm


    Oct 24, 2015 04:58

    Sorry, I don't think it's fixed in 5.2.2f1
    To reproduce Create a new Unity 2D project
    Right click under the Main Camera in the hierarchy, and "Create Empty"
    Right click the new GameObject and Delete
    Exit Unity and Make sure you save your Scene as you do.
    Reopen that project in Unity -> Errors.

  5. 9d3f809669e5688b40064fd8795f1540?d=mm


    Oct 19, 2015 18:40

    I have the problem as well. It is on a 2D project (brand new)

  6. 4f23f5b20606e16bdd8cb2a4e22b2d7c?d=mm


    Oct 14, 2015 17:03

    I still get this error in 5.2.1p3 in both a 3d and 2d projects.

    Screen position out of view frustum (screen pos 0.000000, 0.000000, 0.300000) (Camera rect 0 0 0 0)

  7. 5658e92cec85151c95625cfcba8a003e?d=mm


    Oct 07, 2015 22:56

    I get this message when opening 2D project on (5.2.1f1)
    Screen position out of view frustum (screen pos 0.000000, 0.000000, 0.300000) (Camera rect 0 0 0 0)UnityEditor.DockArea:OnGUI()
    if you change the camera to perspective and restart unity it disappears until you return the orthogonal camera

  8. 6d4c790ea2ce4ef48de096d0083e0e85?d=mm


    Oct 03, 2015 15:39

    on a side note my raycasts all seem to be offset, assuming it goes along with this error, the raycast can be away from the collider and still register a hit, or be accually hitting the collider and NOT register a hit

  9. 6d4c790ea2ce4ef48de096d0083e0e85?d=mm


    Oct 03, 2015 14:07

    getting this in my project as well, 2d, 5.2.0f3

  10. 79fec3947e3c431f572e35a21d7bef10?d=mm


    Oct 02, 2015 15:07

    Same here tons of this errors. Also having big performance lose and mosaic on some static scenes when building for android tested in several devices.

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.