Objects become hidden when navigating the viewport #112532

New Issue

pooya-heydari · 2023-09-18T17:04:49+02:00

pooya-heydari commented

2023-09-18 17:04:49 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-10 22:17, hash: fca8df9415b1
Worked: (newest version of Blender that worked as expected)

Short description of error
when I move inside the viewport, some objects become hidden.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-10 22:17, hash: `fca8df9415b1` Worked: (newest version of Blender that worked as expected) **Short description of error** when I move inside the viewport, some objects become hidden. <video src="/attachments/124ee3a4-adc5-4c91-b2ef-c939f55c4b4f" controls></video>

18.09.2023_18.30.05_REC.mp4

793 KiB

pooya-heydari added the

labels 2023-09-18 17:04:50 +02:00

Jesse Yurkovich commented

2023-09-18 21:11:44 +02:00

Can you attach the problematic .blend file? I'm not able to reproduce the problem using a few objects here.

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-09-18 21:11:52 +02:00

pooya-heydari commented

2023-09-18 22:07:45 +02:00

Can you attach the problematic .blend file? I'm not able to reproduce the problem using a few objects here.

Sure.

> Can you attach the problematic .blend file? I'm not able to reproduce the problem using a few objects here. Sure.

A 007.blend

1.1 MiB

Jesse Yurkovich commented

2023-09-18 22:17:18 +02:00

This is due to the Viewport "Clip End" distance being set way too large, causing loss of precision in the depth buffer. Change it to something more reasonable like 10000 rather than 800000.

pooya-heydari commented

2023-09-18 23:56:31 +02:00

This is due to the Viewport "Clip End" distance being set way too large, causing loss of precision in the depth buffer. Change it to something more reasonable like 10000 rather than 800000.

but in Blender 3.6 it works fine with 800000 for "Clip End".

> This is due to the Viewport "Clip End" distance being set way too large, causing loss of precision in the depth buffer. Change it to something more reasonable like 10000 rather than 800000. but in Blender 3.6 it works fine with 800000 for "Clip End".

Jesse Yurkovich commented

2023-09-19 00:11:42 +02:00

It is still the case that it is too large and there's explicit material in the manual for setting an appropriate clip distance. 800 km is a bit too much considering the Clip start is set to just 0.01 m. https://docs.blender.org/manual/en/dev/editors/3dview/sidebar.html#view-panel

Still, @pragma37 might know if the Workbench engine in 4.0 is somehow more susceptible to precision issues now.

It is still the case that it is too large and there's explicit material in the manual for setting an appropriate clip distance. 800 km is a bit too much considering the Clip start is set to just 0.01 m. https://docs.blender.org/manual/en/dev/editors/3dview/sidebar.html#view-panel Still, @pragma37 might know if the Workbench engine in 4.0 is somehow more susceptible to precision issues now.

pooya-heydari commented

2023-09-19 00:30:19 +02:00

@deadpin thank you .

Miguel Pozo commented

2023-09-19 15:24:36 +02:00

While setting such a wide clip range is indeed asking for troubles and should be avoided, this doesn't look like a depth buffer precision issue to me.
The same problem is in EEVEE Next as well, so if I had to guess I'd say this is probably a frustum culling bug in the new draw manager.

While setting such a wide clip range is indeed asking for troubles and should be avoided, this doesn't look like a depth buffer precision issue to me. The same problem is in EEVEE Next as well, so if I had to guess I'd say this is probably a frustum culling bug in the new draw manager.

👍 1

Miguel Pozo added

and removed

Needs Information from User

Type

Report

labels 2023-09-19 15:25:26 +02:00

Miguel Pozo commented

2023-09-19 17:08:34 +02:00

I took a look at this and the issue is that View::frustum_boundbox_calc, View::frustum_culling_planes_calc and View::frustum_culling_sphere_calc generate NaNs with such extreme projection matrices.

However, they're supposed to be more precise for the common cases than the previous implementation.
So given that using such a wide clipping range is going to cause other types of troubles anyway, I'm not sure if it's worth trying to fix this.

I guess it's a decision that should be taken by @fclem.

I took a look at this and the issue is that `View::frustum_boundbox_calc`, `View::frustum_culling_planes_calc` and `View::frustum_culling_sphere_calc` generate NaNs with such extreme projection matrices. However, they're supposed to be more precise for the common cases than the previous implementation. So given that using such a wide clipping range is going to cause other types of troubles anyway, I'm not sure if it's worth trying to fix this. I guess it's a decision that should be taken by @fclem.

Iliya Katushenock added the

Module

EEVEE & Viewport

label 2023-09-19 18:22:18 +02:00

Clément Foucault commented

2023-09-25 16:35:58 +02:00

@pragma37 I think there should be a way to disable the checks if this happens or fallback to something more conservative. I don't think flickering / hiding meshes are acceptable.

Germano Cavalcante changed title from ~~viewport problem~~ to Objects become hidden when navigating the viewport

2023-10-27 16:31:04 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Objects become hidden when navigating the viewport #112532