Jagged object's contour in 3D View #53973

New Issue

Riccardo Giovanetti · 2018-02-01T12:55:38+01:00

2018-02-01 12:55:38 +01:00

System Information
ASUS G752VS, i7-6820HK, Windows 10 Pro (1511) 64bit, 32GB RAM, Nvidia GTX1070 8GB VRAM (390.77)

Blender Version
Broken: 2.79.2 (Hash: 10fec1f) 64bit
Worked: 2.79 official, 2.79a RC

Short description of error
Object's contour in the 3D View has jagged edges and changing settings in User Preferences | System | Selection/Anisotropic Filterig/Window Draw Method seems to have no effect. I tried any possible combination unsuccessfully.

Exact steps for others to reproduce the error
There's no specifc step to follow. Find below a screenshot of the issue with the User Preferences' settings.

**System Information** ASUS G752VS, i7-6820HK, Windows 10 Pro (1511) 64bit, 32GB RAM, Nvidia GTX1070 8GB VRAM (390.77) **Blender Version** Broken: 2.79.2 (Hash: 10fec1f) 64bit Worked: 2.79 official, 2.79a RC **Short description of error** Object's contour in the 3D View has jagged edges and changing settings in User Preferences | System | Selection/Anisotropic Filterig/Window Draw Method seems to have no effect. I tried any possible combination unsuccessfully. **Exact steps for others to reproduce the error** There's no specifc step to follow. Find below a screenshot of the issue with the User Preferences' settings. ![jagged_edges_2.79.2.jpg](https://archive.blender.org/developer/F2072949/jagged_edges_2.79.2.jpg)

Riccardo Giovanetti commented

2018-02-01 12:55:38 +01:00

Added subscriber: @Harvester

Vuk Gardašević commented

2018-02-01 13:21:43 +01:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2018-02-01 13:21:43 +01:00

This seems like a float precision issue. Check your N region (panel on the right) > View > Clip values.

I can recreate the issue by setting the Start value to 0.00001.

As those issue are related to float precision i'm not sure how them should be solved without changing the precision which will use more memory, however this issue could be related to clamping to a minimum value that doesn't produce artifacts.

Anyway, please let us know if resetting the Clip values solve the issue.

Marking as incomplete until additional information is given.

This seems like a float precision issue. Check your N region (panel on the right) > View > Clip values. I can recreate the issue by setting the Start value to 0.00001. ![view_clip_value_artifacts.png](https://archive.blender.org/developer/F2073308/view_clip_value_artifacts.png) As those issue are related to float precision i'm not sure how them should be solved without changing the precision which will use more memory, however this issue could be related to clamping to a minimum value that doesn't produce artifacts. Anyway, please let us know if resetting the Clip values solve the issue. Marking as incomplete until additional information is given.

Riccardo Giovanetti commented

2018-02-01 14:39:53 +01:00

I confirm that the source of the issue is in the Clip Start value, which was set at 1mm. I will take it in consideration for the future, and from my side you can close this ticket and better spend developers' valuable time. Thank you for addressing me to the source of the problem.

Bastien Montagne commented

2018-02-01 17:13:57 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2018-02-01 17:13:57 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2018-02-01 17:13:57 +01:00

Bastien Montagne self-assigned this 2018-02-01 17:13:57 +01:00

Bastien Montagne commented

2018-02-01 17:13:57 +01:00

Indeed not really a bug, and imho it’s more valuable to allow some extreme values that may come in handy in some cases, even if at the cost of a minor 3DView glitch… Thanks for the report anyway. :)

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

Jagged object's contour in 3D View #53973