Z-Fighting in 3DView (Wireframe Mode) #61803

New Issue

bithunter · 2019-02-21T13:06:09+01:00

bithunter commented

2019-02-21 13:06:09 +01:00

System Information
Operating system:
Windows 10 Pro 64Bit

Graphics card:
GeForce GTX 1070, Nvidia 416.94

Blender Version
2.80, 1af810b4ff 2019-02-20

Short description of error
Sometimes z-fighting in 3DView wireframe mode is visible when faces overlap. Does not happen consistently. E.g. unscaled duplicates don't show this behavior. Compared to 2.79 z-fighting did never happen in wireframe (obviously).

Exact steps for others to reproduce the error
Toggle into wireframe mode:

duplicate default cube, use S(cale) -1
duplicate default cube, add boolean modifier (Intersect) to duplicate and choose original cube as target object
duplicate default cube, set cursor to a vertex, set cursor as pivot, scale duplicate

**System Information** Operating system: Windows 10 Pro 64Bit Graphics card: GeForce GTX 1070, Nvidia 416.94 **Blender Version** 2.80, 1af810b4ff17 2019-02-20 **Short description of error** Sometimes z-fighting in 3DView wireframe mode is visible when faces overlap. Does not happen consistently. E.g. unscaled duplicates don't show this behavior. Compared to 2.79 z-fighting did never happen in wireframe (obviously).![zfightingwire.png](https://archive.blender.org/developer/F6678343/zfightingwire.png) **Exact steps for others to reproduce the error** Toggle into wireframe mode: 1. duplicate default cube, use S(cale) -1 2. duplicate default cube, add boolean modifier (Intersect) to duplicate and choose original cube as target object 3. duplicate default cube, set cursor to a vertex, set cursor as pivot, scale duplicate

bithunter commented

2019-02-21 13:06:09 +01:00

Added subscriber: @bithunter64

Sebastian Parborg commented

2019-02-21 17:19:57 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-02-21 17:19:57 +01:00

Can you upload a .blend file with this problem?

Jacques Lucke commented

2019-02-21 17:20:29 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-21 17:20:29 +01:00

Could you prepare and upload a .blend file that shows the issue, please?

In general, it might not be possible to solve all the z-fighting problems..

[EDIT] you were faster...

Could you prepare and upload a .blend file that shows the issue, please? In general, it might not be possible to solve all the z-fighting problems.. [EDIT] you were faster...

bithunter commented

2019-02-21 17:43:09 +01:00

This is what I see. ~~Haven't had time to test on Linux yet. ~~ Same behavior on Ubuntu 18.04.1 LTS, Nvidia 415.18, GeForce GTX 1070. I'm aware that this one might be hard to fix. Just leaving it here for reference.

zfighting.blend

Seems to be related to outline, which is enabled by default.

![zfighting.png](https://archive.blender.org/developer/F6679941/zfighting.png) This is what I see. ~~Haven't had time to test on Linux yet. ~~ Same behavior on Ubuntu 18.04.1 LTS, Nvidia 415.18, GeForce GTX 1070. I'm aware that this one might be hard to fix. Just leaving it here for reference. [zfighting.blend](https://archive.blender.org/developer/F6679947/zfighting.blend) Seems to be related to **outline**, which is enabled by default.

Clément Foucault was assigned by Sebastian Parborg

2019-02-22 10:39:16 +01:00

Clément Foucault commented

2019-02-22 13:44:20 +01:00

This is due to the outline algorithm not the wireframe. You can disable it in the shading popover.

I cannot consider this a bug. Zfighting is a problem in all rasterization pipeline.

But I could argue that the outline algorithm should be disable by default. It is not useful in a lot of cases and take a bit of performance away.

This is due to the outline algorithm not the wireframe. You can disable it in the shading popover. I cannot consider this a bug. Zfighting is a problem in all rasterization pipeline. But I could argue that the outline algorithm should be disable by default. It is not useful in a lot of cases and take a bit of performance away.

Clément Foucault commented

2019-02-22 13:44:36 +01:00

Changed status from 'Open' to: 'Archived'

Clément Foucault closed this issue

2019-02-22 13:44:36 +01:00

bithunter commented

2019-02-22 14:04:29 +01:00

I guess outlines - while useful in solid mode - are not useful for wireframe mode because they give no visual cue for cases where overlaps are backfacing.
E.g. For front facing overlaps they just clutter the view even more.
If there is one thing you don't want in wireframe mode it is more lines than needed. So it might be best
to give options to toggle outlines for solid and wireframe mode separatly or remove it from wireframe altogether(?). Just my thoughts.

I guess outlines - while useful in solid mode - are not useful for wireframe mode because they give no visual cue for cases where overlaps are backfacing. E.g. ![outline1.png](https://archive.blender.org/developer/F6686639/outline1.png) For front facing overlaps they just clutter the view even more. If there is one thing you don't want in wireframe mode it is more lines than needed. So it might be best to give options to toggle outlines for solid and wireframe mode separatly or remove it from wireframe altogether(?). Just my thoughts.

Clément Foucault commented

2019-02-22 16:44:32 +01:00

Added subscriber: @WilliamReynish

Clément Foucault commented

2019-02-22 16:44:32 +01:00

I propose de get rid of the option when in wireframe mode. It is clear that it adds confusion. @WilliamReynish what do you think?

William Reynish commented

2019-02-23 02:17:15 +01:00

@fclem I agree. If we are using brightness for selection anyway, the outline doesn’t have much reason for being.

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

Z-Fighting in 3DView (Wireframe Mode) #61803