Aliased wireframes + modifier edit mode display issue #105582

Open
opened 2023-03-09 05:59:20 +01:00 by Paul Kotelevets · 16 comments

System Information
Operating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits
Graphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
2.90
Worked: 2.79, 2.81

Short description of error
Edit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.

Steps to reproduce

  • Open file
  • Disable all anti-aliasing and smoothing in preferences > Viewport > Quality

Selection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.

**System Information** Operating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits Graphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `rB55485cb379f7` 2.90 Worked: 2.79, 2.81 **Short description of error** Edit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range. **Steps to reproduce** * Open file * Disable all anti-aliasing and smoothing in preferences > Viewport > Quality Selection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.
Paul Kotelevets added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-03-09 05:59:21 +01:00
Paul Kotelevets changed title from Aliased wireframes display edit mode issue to Aliased wireframes edit mode display issue 2023-03-09 06:06:30 +01:00
Paul Kotelevets changed title from Aliased wireframes edit mode display issue to Aliased wireframes bevel modifier edit mode display issue 2023-03-09 06:21:35 +01:00
Paul Kotelevets changed title from Aliased wireframes bevel modifier edit mode display issue to Aliased wireframes + modifier edit mode display issue 2023-03-09 06:22:51 +01:00
Member

Hi, thanks for the report. This is same as #64915, closing. (both shows aliasing problem with mirror modifier)
Feel free to comment or reopen the report if there is misunderstanding.

Hi, thanks for the report. This is same as #64915, closing. (both shows aliasing problem with mirror modifier) Feel free to comment or reopen the report if there is misunderstanding.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-03-09 14:43:54 +01:00
Pratik Borhade added
Status
Duplicate
and removed
Status
Archived
labels 2023-03-09 14:44:01 +01:00

Hi, thanks for the report. This is same as #64915, closing. (both shows aliasing problem with mirror modifier)
Feel free to comment or reopen the report if there is misunderstanding.

I think it is a quite different issue from mentioned above, this one is about the case when antialiasing is not used on purpose at all, and another is about the cases when antialiasing is used but broken.

Aliased wireframes are commonly used for workflows that require visual checking of a verticality, horizontality and microangles during mesh modeling (CAD workflows domain - architecture, manufacturing, etc)

Since visual accuracy of an aliased wireframes display is a workflow demand, I would prefer to reopen it, because both issues has different goals, has different requirements to satisfy and may require different solutions.

> Hi, thanks for the report. This is same as #64915, closing. (both shows aliasing problem with mirror modifier) > Feel free to comment or reopen the report if there is misunderstanding. I think it is a quite different issue from mentioned above, this one is about the case when antialiasing is not used on purpose at all, and another is about the cases when antialiasing is used but broken. Aliased wireframes are commonly used for workflows that require visual checking of a verticality, horizontality and microangles during mesh modeling (CAD workflows domain - architecture, manufacturing, etc) Since visual accuracy of an aliased wireframes display is a workflow demand, I would prefer to reopen it, because both issues has different goals, has different requirements to satisfy and may require different solutions.
Blender Bot added
Status
Needs Triage
and removed
Status
Duplicate
labels 2023-03-14 03:08:46 +01:00

I can't confirm the issue from the screenshot in the example. Unless you mean something like that?
image

I can't confirm the issue from the screenshot in the example. Unless you mean something like that? ![image](/attachments/e801d0f2-81eb-42d7-b259-7c4cf55a3834)
1.4 MiB

I can't confirm the issue from the screenshot in the example. Unless you mean something like that?
image

It looks like your wireframes has antialiasing enabled. You need to turn it off to reproduce.

> I can't confirm the issue from the screenshot in the example. Unless you mean something like that? > ![image](/attachments/e801d0f2-81eb-42d7-b259-7c4cf55a3834) It looks like your wireframes has antialiasing enabled. You need to turn it off to reproduce.

@1D_Inc I turned it on just to find something. I can't reproduce the original way

@1D_Inc I turned it on just to find something. I can't reproduce the original way

@1D_Inc I turned it on just to find something. I can't reproduce the original way

Can you paste a screenshot with aliased wireframes and no original described problem on it, please?
I used the latest official release, but also tried 3.3.4 LTS

image

> @1D_Inc I turned it on just to find something. I can't reproduce the original way Can you paste a screenshot with aliased wireframes and no original described problem on it, please? I used the latest official release, but also tried 3.3.4 LTS ![image](/attachments/bb850e79-dc2f-4c67-a273-7e7c7be16587)
716 KiB
3.3 3.6
image image
| 3.3 | 3.6 | | -------- | -------- | | ![image](/attachments/308929b5-5a7c-45e9-85cd-66f664e065b1) | ![image](/attachments/4f46e88a-39b6-4564-a03c-d131e94a129f) |
1.5 MiB
1.5 MiB

@mod_moder
They still look very antialiased.
You need to turn off smooth wires edit mode checkbox in viewport preferences (like on my latest screenshot), save preferences and restart Blender to apply changes.

@mod_moder They still look very antialiased. You need to turn off smooth wires edit mode checkbox in viewport preferences (like on my latest screenshot), save preferences and restart Blender to apply changes.

I guess this is result of having 2 edge drawing engines (at least from how I understand this is done now). This may be a limitation of current system, but will confirm.

Edit: actually now I read the issue more closely, when I disable modifier in edit mode, there is no z fighting, so I am even less sure about why this happens. But still I think this is valid issue

I guess this is result of having 2 edge drawing engines (at least from how I understand this is done now). This may be a limitation of current system, but will confirm. Edit: actually now I read the issue more closely, when I disable modifier in edit mode, there is no z fighting, so I am even less sure about why this happens. But still I think this is valid issue

It looks like pretty heavy limitation.

It looks like pretty heavy limitation.
Richard Antalik added
Module
EEVEE & Viewport
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-03-16 07:27:25 +01:00

I have edited the comment a bit, but still could be, that these lines are drawn in passes, so there are issues with blending them.

I have edited the comment a bit, but still could be, that these lines are drawn in passes, so there are issues with blending them.

Yes, there are issues with blending/drawordering them that results in flickering and z-fighting of a selection drawing and drawing a wireframe behind it.

Yes, there are issues with blending/drawordering them that results in flickering and z-fighting of a selection drawing and drawing a wireframe behind it.

This only happens with modifiers
изображение
изображение
An additional outline appears
изображение
Video: https://youtu.be/m3VrigOhpiw

This only happens with modifiers ![изображение](/attachments/6acb5642-9aec-4a71-a115-d526797e5245) ![изображение](/attachments/e9b70388-5082-45d3-9c8c-be040c3ae24d) An additional outline appears ![изображение](/attachments/9ad3843b-6bbb-4f62-b5cb-13c2b08981de) Video: https://youtu.be/m3VrigOhpiw

this has always been broken, since version 2.80. As I understand it, there is a slight shift due to which the overlay effect occurs.

this has always been broken, since version 2.80. As I understand it, there is a slight shift due to which the overlay effect occurs.

Yes, such an effect injures proper mesh readability which makes modeling since 2.8 harder, especially modeling from references and in case when aliasing is used (for example, for detecting accidental skews in straight geometry)

Yes, such an effect injures proper mesh readability which makes modeling since 2.8 harder, especially modeling from references and in case when aliasing is used (for example, for detecting accidental skews in straight geometry)

Yes, such an effect injures proper mesh readability which makes modeling since 2.8 harder, especially modeling from references and in case when aliasing is used (for example, for detecting accidental skews in straight geometry)

It's a shame that we have to wait years for such basic fixes. Do their artists really not see this as a problem at all? Moreover, all this has been going on since 2.8. Are there really no people on their team who worked in 2.7? They need to stop making simple cartoons, and start making something technologically advanced with small details and a dense mesh.

> Yes, such an effect injures proper mesh readability which makes modeling since 2.8 harder, especially modeling from references and in case when aliasing is used (for example, for detecting accidental skews in straight geometry) It's a shame that we have to wait years for such basic fixes. Do their artists really not see this as a problem at all? Moreover, all this has been going on since 2.8. Are there really no people on their team who worked in 2.7? They need to stop making simple cartoons, and start making something technologically advanced with small details and a dense mesh.
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#105582
No description provided.