Object wireframe clips through mesh when working at smaller scales than default #59978

Closed
opened 2018-12-30 05:45:40 +01:00 by eldee smith · 16 comments

System Information
Operating system: Kubuntu 18.10, Windows 10
Graphics card: 1080TI

Blender Version
Broken: 2.80, 6d89337257, blender2.7, 2018-12-24 14:03

Short description of error
When working at smaller scales, the default clipping plane is too far away and must be reduced. Mesh wireframes do not appear to take this new clipping plane into consideration and cause backface wires display through the mesh when zoomed out. (See video below repro steps)
It does not happen while the viewport is rotating, which leads me to believe this is related to wireframe anti-aliasing but I could not test it with AA disabled because unlike UI text there's no way to disable it (HINT HINT)

Exact steps for others to reproduce the error

  • Set the scene units to Centimeters
  • Subdivide the default cube a few times to create some geometry to work with
  • Set the cube's dimensions to 10cm and apply the scale
  • Change the near clipping plane to .01mm
  • Observe the backface wires showing through the mesh.
  • Rotate the viewport and note that the backface wires disappear as long as the viewport is moving
  • Change the near clipping plane to 1mm
  • Zoom in and out to see the effect increase and decrease in intensity, though noticeably less than when the near clipping plane was set to .01mm

wireframe_small_objects.mp4

**System Information** Operating system: Kubuntu 18.10, Windows 10 Graphics card: 1080TI **Blender Version** Broken: 2.80, 6d89337257b6, blender2.7, 2018-12-24 14:03 **Short description of error** When working at smaller scales, the default clipping plane is too far away and must be reduced. Mesh wireframes do not appear to take this new clipping plane into consideration and cause backface wires display through the mesh when zoomed out. (See video below repro steps) It does not happen while the viewport is rotating, which leads me to believe this is related to wireframe anti-aliasing but I could not test it with AA disabled because unlike UI text there's no way to disable it (HINT HINT) **Exact steps for others to reproduce the error** - Set the scene units to Centimeters - Subdivide the default cube a few times to create some geometry to work with - Set the cube's dimensions to 10cm and apply the scale - Change the near clipping plane to .01mm - Observe the backface wires showing through the mesh. - Rotate the viewport and note that the backface wires disappear as long as the viewport is moving - Change the near clipping plane to 1mm - Zoom in and out to see the effect increase and decrease in intensity, though noticeably less than when the near clipping plane was set to .01mm [wireframe_small_objects.mp4](https://archive.blender.org/developer/F6113449/wireframe_small_objects.mp4)
Author

Added subscriber: @testure

Added subscriber: @testure

#61139 was marked as duplicate of this issue

#61139 was marked as duplicate of this issue

#60827 was marked as duplicate of this issue

#60827 was marked as duplicate of this issue

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2018-12-31 15:33:08 +01:00

This is sadly how clipping values work. Small clipping values will produce errors. There is no getting around that.

This is sadly how clipping values work. Small clipping values will produce errors. There is no getting around that.
Author

In #59978#590863, @ZedDB wrote:
This is sadly how clipping values work. Small clipping values will produce errors. There is no getting around that.

Wait, what? I dont' mean to offend, but did you even watch my demonstration? The artifacts disappear while the viewport is being rotated, so clearly something else is going on. It has nothing to do with normal geometry clipping- it's only happening on wireframes while the viewport is stationary.

It's a little frustrating to spend the time making detailed bug reports and coming up with clear repro steps if they're not even looked at.

edit: look at timecode 1:00 in my video

> In #59978#590863, @ZedDB wrote: > This is sadly how clipping values work. Small clipping values will produce errors. There is no getting around that. Wait, what? I dont' mean to offend, but did you even watch my demonstration? The artifacts disappear while the viewport is being rotated, so *clearly* something else is going on. It has nothing to do with normal geometry clipping- it's only happening on wireframes while the viewport is stationary. It's a little frustrating to spend the time making detailed bug reports and coming up with clear repro steps if they're not even looked at. edit: look at timecode 1:00 in my video
Sebastian Parborg removed their assignment 2018-12-31 17:26:57 +01:00
Clément Foucault was assigned by Sebastian Parborg 2018-12-31 17:26:57 +01:00

Sorry, you are right. I should have read and watched the bug report more carefully.
There does indeed seem to be something going on with the static edge drawing that doesn't happen when moving around.

Sorry, you are right. I should have read and watched the bug report more carefully. There does indeed seem to be something going on with the static edge drawing that doesn't happen when moving around.

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

No worries, thanks for taking another look!

No worries, thanks for taking another look!

Added subscribers: @HardRooster, @MauricioMarinho

Added subscribers: @HardRooster, @MauricioMarinho

Added subscriber: @gentleclockdivider

Added subscriber: @gentleclockdivider

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Fixed by commiting the refactor of edit mode drawing. 86193d25db

Fixed by commiting the refactor of edit mode drawing. 86193d25db

Added subscriber: @Russ1642

Added subscriber: @Russ1642

Is this fix in the latest build because I'm still seeing an x-ray view of edges in orthographic mode with x-ray turned off?

Is this fix in the latest build because I'm still seeing an x-ray view of edges in orthographic mode with x-ray turned off?
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#59978
No description provided.