Too high clipping range + Auto Depth may send view location to oblivion #71795

New Issue

Stanislav Blinov · 2019-11-23T00:46:05+01:00

Stanislav Blinov commented

2019-11-23 00:46:05 +01:00

Blender Version
Broken: 2.80, 2.81, 2.82 (04272613a7)
Worked: 2.79b

Short description of error
If Auto-Depth preference is enabled, and there's very large clipping range for current view, then panning, rotating or zooming view while having mouse pointer over any geometry may result in view matrix translation component becoming 3 nans.

Exact steps for others to reproduce the error

Load the default scene.
In user preferences, enable Navigation -> Auto Depth
In side bar, View, set clip start to 0.001 and clip end to 100000
Place mouse pointer over the cube
Try panning, rotating or zooming the view

View will end up "nowhere" (can be restored by focusing on selected). region_data.view_matrix will have its translation component a vector of 3 nans.

Granted, extreme clipping ranges should be avoided, but the program should at least react somehow to obviously invalid view matrix. And the behavior seems to be a regression from 2.79b.

**Blender Version** Broken: 2.80, 2.81, 2.82 (04272613a78d) Worked: 2.79b **Short description of error** If Auto-Depth preference is enabled, and there's very large clipping range for current view, then panning, rotating or zooming view while having mouse pointer over any geometry may result in view matrix translation component becoming 3 nans. **Exact steps for others to reproduce the error** 1. Load the default scene. 2. In user preferences, enable Navigation -> Auto Depth 3. In side bar, View, set clip start to 0.001 and clip end to 100000 4. Place mouse pointer over the cube 5. Try panning, rotating or zooming the view View will end up "nowhere" (can be restored by focusing on selected). region_data.view_matrix will have its translation component a vector of 3 nans. Granted, extreme clipping ranges should be avoided, but the program should at least react somehow to obviously invalid view matrix. And the behavior seems to be a regression from 2.79b.

Stanislav Blinov commented

2019-11-23 00:46:05 +01:00

Added subscriber: @Stan_Pancakes

Stanislav Blinov commented

2019-11-23 02:24:01 +01:00

See also https://blenderartists.org/t/the-case-of-the-disappearing-viewport-2-81/1192223 for slightly different behavior (seems not to be affected by Auto Depth).

Kevin Handy commented

2019-11-24 18:44:41 +01:00

Added subscriber: @Kevin-Handy

Kevin Handy commented

2019-11-24 18:44:41 +01:00

I'm the user with the related issue referenced by @radcapricorn. The fix offered on that thread did indeed work. Updated notes on my issue:

Worked on 2.80
Failed on 2.81-125257758007 beta through current 2.81 release
adjusted ONLY the Clip Start to 1' (a number smaller than suggested), left Clip End at 3281', Frame Selected, viewport works as expected.

It appears that my part of the issue is only related to the Clip Start. My part also did not present itself initially despite the Clip Range being so high. Only after a couple of hours of concept work in the file did the issue present.

I'm the user with the related issue referenced by @radcapricorn. The fix offered on that thread did indeed work. Updated notes on my issue: - Worked on 2.80 - Failed on 2.81-125257758007 beta through current 2.81 release - adjusted ONLY the Clip Start to 1' (a number smaller than suggested), left Clip End at 3281', Frame Selected, viewport works as expected. It appears that my part of the issue is only related to the Clip Start. My part also did not present itself initially despite the Clip Range being so high. Only after a couple of hours of concept work in the file did the issue present.

Germano Cavalcante commented

2019-11-26 20:08:45 +01:00

Added subscriber: @mano-wii