Search Issue Tracker
Duplicate
Votes
44
Found in
5.3.0b4
Issue ID
740602
Regression
No
[Assert] Screen position out of view frustum error printed non stop (Camera::ScreenPointToRay or Camera::ScreenToWorldPoint)
Open Scenes\level1.unity in the attached project and press Play. Notice how the Console gets spammed with "Screen position out of view frustum" errors:
Screen position out of view frustum (screen pos 0.000000, 0.000000, 1555688.750000) (Camera rect 0 0 256 256)
UnityEngine.Camera:Render()
UnityStandardAssets.Water.Water:OnWillRenderObject() (at Assets/MiniGolf/Standard Assets/Environment/Water/Water/Scripts/Water.cs:108)
UnityEditor.DockArea:OnGUI()
Recommendation:
If there are resources for it, add support for double precision to the relevant methods. Otherwise, clamp the far clip plane to never be larger than 1000000 (same max value it had before).
Comments (57)
-
GroverGarcia
May 20, 2020 07:00
Around the world, a huge crowd wants to read this type of post especially for those who relate this type of field I am also part of them, and the post is proven very helpful for me. https://www.michaeljacksoncostume.com/product/michael-jackson-blood-on-the-dance-floor-jacket/
-
kevinbear741
Feb 20, 2020 12:40
get good now look at him he the real goat bro Very interesting information post dude
https://www.usajacket.com/product/ralph-breaks-internet-mulan-red-jacket/ -
toolparaphrase
Jan 12, 2020 18:35
Having this issue in 5.3.2f1. Even removing default from the reflection mask doesn't help. Only if I deactivate the Planar Reflection script does it go away.
https://paraphrase.rewriter-tool.com/
https://seotoolcheckers.com/grammar-checker
https://paraphrasingstool.com/
https://seotoolcheckers.com/mobile-friendly-test -
Meceka
Nov 11, 2019 17:39
I have written how we fixed this issue in this forum post.
https://forum.unity.com/threads/solved-screen-position-out-of-view-frustum.60851/page-2#post-5163704 -
thefallengamesstudio
May 17, 2018 21:06
For anyone that may have a similar error message as we had: https://forum.unity.com/threads/solved-screen-position-out-of-view-frustum.60851/#post-3500789
-
nikix22
Mar 15, 2018 12:46
Try with this fix! :)
In Water.cs you have 2 places with this calls (in function OnWillRenderObject() ) :
...
reflectionCamera.Render();
...
refractionCamera.Render();
...Just add condition before render like this:
....
if (!reflectionCamera.orthographic)
refractionCamera.Render();
...
if (!refractionCamera.orthographic)
refractionCamera.Render();
....this worked for me, and rendering still works even in Editor window, all without errors.
Cheers! -
Nazowa
Nov 25, 2017 12:58
Assertion failed: Screen position out of view frustum (screen pos 0.000000, 0.000000, 1000.000000) (Camera rect 0 0 795 415)
UnityEngine.Camera:Render()
Assertion failed: Screen position out of view frustum (screen pos 0.000000, 415.000000, 1000.000000) (Camera rect 0 0 795 415)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)Take your pick. This has reincarnations in various flavors.
-
lexipwodahS
Nov 09, 2017 01:42
i have 5.5.0 and i get this error when i follow the survival shooter tutorial made by unity. It happened when i switched the camera to orthographic mode.
-
Brozef
Oct 27, 2016 18:24
For me this was only showing up in the Console when my Editor camera was in 2D mode. So if you are playing the game in the editor and your editor camera is in 2D mode just switch it back to 3D and the error goes away.
-
DeadShawn
Feb 28, 2016 02:08
Just upgraded to 5.3.3f1, still having the issue
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
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
- Copying and pasting Animator Transitions leads to unexpected behaviour
- "ShaderGraph" misses a space in the "Project Settings" section
- UI Builder inspector’s checkbox fields can be activated when clicking anywhere in the value field
This is a duplicate of issue #801555