Interface (Solid & Preview) Display Bug with Low Clipping Values #81311

New Issue

Will Jackson · 2020-09-30T03:33:10+02:00

Will Jackson commented

2020-09-30 03:33:10 +02:00

System Information
Operating system: Windows 10 Pro 64 bit
Graphics card: ASUS Strix GeForce GTX 1060 OC edition 6GB

Blender Version
Broken: Versions 2.82, 2.83, 2.90
Worked: N/A

Short description of error
Display issue where meshes appear to intersect, partially dissolve, and to have pieces missing, despite retaining original properties. The world grid also appears and disappears depending on zoom distance.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

To reproduce the error, one has to set the 'clip start' value to 0.000001 m or lower.

Bugged Blend File.blend

**System Information** Operating system: Windows 10 Pro 64 bit Graphics card: ASUS Strix GeForce GTX 1060 OC edition 6GB **Blender Version** Broken: Versions 2.82, 2.83, 2.90 Worked: N/A **Short description of error** Display issue where meshes appear to intersect, partially dissolve, and to have pieces missing, despite retaining original properties. The world grid also appears and disappears depending on zoom distance. ![Screenshot (32).png](https://archive.blender.org/developer/F8938237/Screenshot__32_.png) ![Screenshot (33).png](https://archive.blender.org/developer/F8938238/Screenshot__33_.png) **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible). To reproduce the error, one has to set the 'clip start' value to 0.000001 m or lower. ![image.png](https://archive.blender.org/developer/F8938274/image.png) [Bugged Blend File.blend](https://archive.blender.org/developer/F8938267/Bugged_Blend_File.blend)

Will Jackson commented

2020-09-30 03:33:10 +02:00

Added subscriber: @SoccerClam2

blender-admin commented

2020-09-30 03:33:10 +02:00

#81309 was marked as duplicate of this issue

Alaska commented

2020-09-30 04:08:51 +02:00

Added subscriber: @Alaska

Alaska commented

2020-09-30 04:08:51 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Alaska closed this issue

2020-09-30 04:08:51 +02:00

Alaska self-assigned this 2020-09-30 04:08:51 +02:00

Alaska commented

2020-09-30 04:08:51 +02:00

Thanks for the report, however there's not much that can be done to resolve this issue.

The issue in question is a "precision issue" bug. When you set your Clip Start value to a really small number, all the precision made available to Blender by your computer components are wasted on the first few millimetres infront of the camera. This leaves small amounts of precision left for rendering objects further away like the sofa in your scene or the default cube. And this lack of precision shows up as the artifacts you seem.

The only way to resolve it is to use a higher level of precision, but the side effect to that is rendering of the viewport will slow down, and potentially by a large amount.

Thanks for the report, however there's not much that can be done to resolve this issue. The issue in question is a "precision issue" bug. When you set your `Clip Start` value to a really small number, all the precision made available to Blender by your computer components are wasted on the first few millimetres infront of the camera. This leaves small amounts of precision left for rendering objects further away like the sofa in your scene or the default cube. And this lack of precision shows up as the artifacts you seem. The only way to resolve it is to use a higher level of precision, but the side effect to that is rendering of the viewport will slow down, and potentially by a large amount.

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

Interface (Solid & Preview) Display Bug with Low Clipping Values #81311