Search Issue Tracker
Fixed in 5.2.2
Votes
45
Found in
5.2.0b3
Issue ID
713457
Regression
Yes
[2D] Screen position out of view frustum errors
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).
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
- [Usability] Not possible to set Editor Window text colour to be default black without workaround
- Text field max length is -1 by default
- Field Max Length is set to the first digit typed instead of entire number typed
- D3D12 MainLight Shadowmap clear incorrectly when using UWP
- Crash on ShaderPropertySheet::SetTexture when changing color space on a specific project
jhepong
Dec 03, 2015 15:33
I'm using 5.2.3f1 and I'm still having this error, though I don't know if this error has effects at all
lior_rosenspitz
Dec 01, 2015 19:13
Happens to me too in v.5.2.3f.
Screen position out of view frustum (screen pos 0.000000, 0.000000, 20.000000) (Camera rect 0 0 0 0)
UnityEditor.DockArea:OnGUI()
Necronomicron
Nov 30, 2015 16:56
5.2.3f1, still present.
lvictorino
Nov 30, 2015 07:29
Not fixed in 5.2.3f1
tosiabunio
Nov 24, 2015 23:31
Still persist in 5.2.3f1: http://prntscr.com/96lf06
Gary Pallett
Nov 23, 2015 19:48
This issue is still present in 5.2.2f1.
1) Selecting the Scene tab as default, closing Unity and re-opening the project causes the issue to re-occur.
2) Selecting the Game tab as default, closing Unity and re-opening the project, it doesn't occur then at all.
So it appears to be a startup issue when the Game tab is default.
kerem-yokuva
Nov 22, 2015 13:07
5.2.3f1 still has it.
PrincipleDev
Nov 13, 2015 14:18
I confirm this is still happening in 5.2.2f1. It does not affect the usage of Unity, or the execution/compilation of any created project. Its more of an annoyance than anything.
unikum.llc
Nov 10, 2015 14:18
it's not fixed in 5.2.2f1
noXur
Nov 10, 2015 13:33
We are confronted with this bug, too. Using Unity 5.2.2f1.