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).
-
Lionious
Feb 11, 2016 10:00
there also problem with Reflec now , that i can't select any game objects on my scene if my water script is on for Reflec that really need srs fix .
-
smile59
Jan 28, 2016 21:01
Hello,
You can put off default reflect layer on your water game object. Error will stop appear. But it's a temporary solution :(
Have a nice day,
Smile -
nasos_333
Jan 27, 2016 08:27
I get the same issue in 5.3.1p4 with the Water4 reflection script from standard assets.
Also i get the "!IsFinite(outDistanceForSort)" error when i use this script with particles with the error pointing in the exact same code line of the "Screen position out of view frustum" error.
-
stigmamax
Jan 23, 2016 15:52
It's not fixed in 5.3.1p4 !!!!!!!!!!!
-
Roman-Ilyin
Dec 02, 2015 12:42
Seems to be fixed in 5.3.0f
-
Roman-Ilyin
Nov 10, 2015 13:46
Same error as
http://issuetracker.unity3d.com/issues/screen-position-out-of-view-frustum-errorsIt's NOT FIXED in 5.2.2(!)
2D project, Ortho camera
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #801555