Search Issue Tracker
Fixed in 7.1.2
Votes
0
Found in [Package]
6.9.0, 7.0.1
Issue ID
1182014
Regression
Yes
Screen position out of view frustum errors thrown when setting Planar Reflection Probe FOV to 0
Repro steps:
1. Open user attached project
2. In the Hierarchy, select "Planar Reflection Probe" object and add a Planar Reflection Probe component
3. In the component's Capture Settings, change the Field Of View Mode to Fixed
4. Change the Value that appeared below Field Of View Mode to 0
Expected result: No errors are thrown
Actual result: Screen position out of view frustum errors are thrown
Reproducible with package versions: 4.10.0 (2018.4.9f1), 5.2.3 (2019.1.0b5), 6.9.0 (2019.2.5f1), 7.0.1 (2020.1.0a4)
Not reproducible with package versions: 5.6.1(2019.1.0b5), 5.16.1 (2019.1.14f1), 6.7.1 (2019.2.0b1)
Could not test with: 5.3.1 (2019.1.0b5) (unrelated errors)
Errors thrown:
Assertion failed on expression: 'IsMatrixValid(matrix)'
Screen position out of view frustum (screen pos 0.000000, 0.000000, 1000.000000) (Camera rect 0 0 1024 1024)
Screen position out of view frustum (screen pos 1024.000000, 0.000000, 1000.000000) (Camera rect 0 0 1024 1024)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment