Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0f2
2019.2.0a1
Issue ID
1147040
Regression
No
"Screen position out of view frustum" errors when Camera's frustum is very narrow and it intersects any GameObject mesh
How to reproduce:
1. Open the attached project "case_1147040-CameraViewportErrors" and scene "testScene"
2. Hover the GameView
3. Observe the Console Window
Expected result: no errors in the Console Window
Actual result: error messages containing string "Screen position out of view frustum" are printed to the Console Window
Reproducible with: 2017.4.26f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a12
Note: the issue only happens when the Camera's Viewport Width or Height is very close to zero. This can be achieved by setting the "Viewport Rect X" or "Viewport Rect Y" fields on the Camera Component to 0.9999 or even closer to 1 so the scene is almost completely out of view or setting the "Viewport Rect W" or "Viewport Rect H" to 0.0001 or closer to 0. The errors are reprinted when the Game View is visible and a new intersection with a Scene GameObject's mesh occurs or when the Game View is hovered
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
- ScalableBufferManager does not work correctly when MSAA and RenderGraph Compatability are enabled
- Sprite artefacts appear when Sprite Packer is enabled
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
Resolution Note:
Setting the viewport to such small numbers is not advised, especially with these numbers it will be smaller than a pixel, at which point a lot of systems will start to complain, ideally you would want to disable the camera before this point or make sure you are at a size where you have at least a pixel being returned.