Visibility problems in Edit mode - Solid view #67484

Closed
opened 2019-07-23 04:09:25 +02:00 by YAFU · 11 comments

System Information
Operating system: Linux-5.0.1-050001-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: 38d4483c6a
Worked: (optional)

Short description of error
In this first file:
viewport_edit mode.blend
It is really difficult to distinguish that the front vertex is selected (that marked under the blue circle). In the other vertices it is also difficult to distinguish which of the vertices are in front or which are behind.

In this other file:
viewport_edit mode_1.blend
On the left, in Vertex select mode the edges coinciding with the blue Z and red X axis are almost invisible. On the right, in that view two of the vertices selected in front appear as not selected. The same in Edge select mode.

**System Information** Operating system: Linux-5.0.1-050001-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: `38d4483c6a` Worked: (optional) **Short description of error** In this first file: [viewport_edit mode.blend](https://archive.blender.org/developer/F7623814/viewport_edit_mode.blend) It is really difficult to distinguish that the front vertex is selected (that marked under the blue circle). In the other vertices it is also difficult to distinguish which of the vertices are in front or which are behind. In this other file: [viewport_edit mode_1.blend](https://archive.blender.org/developer/F7623817/viewport_edit_mode_1.blend) On the left, in Vertex select mode the edges coinciding with the blue Z and red X axis are almost invisible. On the right, in that view two of the vertices selected in front appear as not selected. The same in Edge select mode.
Author

Added subscriber: @YAFU

Added subscriber: @YAFU
Author

By the way, I think it's not good that vertices in front are less prominent and less visible than those at the back in those views in Ortho view. This really makes work difficult. This is working in the opposite way to what it did in 2.79. Not sure if this is by intentional design or a bug.

Edit:
And apparently in Blender 2.8 the behavior seems to depend on Viewpoint, Front is different to Back and Top is different to Botton. I expected Top view to behave like Front, but apparently it is reversed there.
Anyway I clarify that in the original post of the report, when I say "Front", I refer to the side closest to the user, regardless of which Viewpoint we are. In 2.79 it seems that this is not viewpoint dependent, and always vertices closer to the user are always more prominent than the farthest vertices, and I think that is how it should work.

By the way, I think it's not good that vertices in front are less prominent and less visible than those at the back in those views in Ortho view. This really makes work difficult. This is working in the opposite way to what it did in 2.79. Not sure if this is by intentional design or a bug. Edit: And apparently in Blender 2.8 the behavior seems to depend on Viewpoint, Front is different to Back and Top is different to Botton. I expected Top view to behave like Front, but apparently it is reversed there. Anyway I clarify that in the original post of the report, when I say "Front", I refer to the side closest to the user, regardless of which Viewpoint we are. In 2.79 it seems that this is not viewpoint dependent, and always vertices closer to the user are always more prominent than the farthest vertices, and I think that is how it should work.

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2019-07-24 15:55:22 +02:00

This is a limitation of the new viewport render engine. It might be possible to fix, but it is not thing that we will actively look into.

This is a limitation of the new viewport render engine. It might be possible to fix, but it is not thing that we will actively look into.
Author

Hi Sebastian.
I understand that my report may not have been clear because I started with issues that can be considered as design/limitations. Just in case to make it clear that you saw the last case, the verices closest to the user in Front viewpoint are selected, but they look unselected
edit_mode.jpg

This gets even worse if you switch to Back viewpoint and you want to choose one of the three vertices closest to the user in that view.

Otherwise, I hope that view in Ortho view for modelers will have more attention in future releases.
Thank you.

Hi Sebastian. I understand that my report may not have been clear because I started with issues that can be considered as design/limitations. Just in case to make it clear that you saw the last case, the verices closest to the user in Front viewpoint are selected, but they look unselected ![edit_mode.jpg](https://archive.blender.org/developer/F7626716/edit_mode.jpg) This gets even worse if you switch to Back viewpoint and you want to choose one of the three vertices closest to the user in that view. Otherwise, I hope that view in Ortho view for modelers will have more attention in future releases. Thank you.
Sebastian Parborg removed their assignment 2019-07-24 17:51:40 +02:00
Clément Foucault was assigned by Sebastian Parborg 2019-07-24 17:51:40 +02:00

Fine, you win ;)
(This makes otho view quite useless so it should be fixed)

Fine, you win ;) (This makes otho view quite useless so it should be fixed)

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Clément Foucault was unassigned by Dalai Felinto 2019-12-23 16:33:35 +01:00

Added subscriber: @fclem

Added subscriber: @fclem

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Clément Foucault self-assigned this 2020-01-29 21:42:46 +01:00

This has been fixed in 2.82.

This has been fixed in 2.82.
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
4 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#67484
No description provided.