Selection Issues on High Res Monitor #58958

Closed
opened 2018-12-07 18:46:42 +01:00 by Chris Malcheski · 13 comments

{F5874146}System Information
Operating system: Windows Pro 64
Graphics card: nVidia RTX 2080

Blender Version
Broken: 2.80 beta hash 74db65e542
Worked: 2.79b

Short description of error

This is a very general problem in several areas of the display. I'm using a 32" monitor at 3840 x 2160. Selection of objects is extremely problematic. About 95% of the time I have to click the mouse over and over to select the exact object I want. The picking algorithm doesn't pick right. I've fallen into a pattern of clicking until the desired object is selected, then shift-block to deselect what I don't want. The lines are much too thin, even on the user preferences "thick" setting. Very difficult to see. Objects in object mode look sketchy like they were drawn in with a pencil, and when a line appears directly over a grid line, it's practically invisible. Edit mode is slightly better but the vertex squares are also light and sketchy. I have my settings set to 125% display size. The problem was even worse at 100%. The worst problem is missing objects when the left button is clicked. (All of this relates to wireframe.)

There is also another issue but this could be related to my particular mouse: 99% of the time, when I press down on the wheel, the display immediately jumps from ortho to perspective mode. It is infuriating. I am CONSTANTLY hitting num pad 5 to reset ortho mode over and over and over.

Exact steps for others to reproduce the error

{[F5874146](https://archive.blender.org/developer/F5874146/Video_1_Bridge.blend)}**System Information** Operating system: Windows Pro 64 Graphics card: nVidia RTX 2080 **Blender Version** Broken: 2.80 beta hash 74db65e5424 Worked: 2.79b **Short description of error** This is a very general problem in several areas of the display. I'm using a 32" monitor at 3840 x 2160. Selection of objects is extremely problematic. About 95% of the time I have to click the mouse over and over to select the exact object I want. The picking algorithm doesn't pick right. I've fallen into a pattern of clicking until the desired object is selected, then shift-block to deselect what I don't want. The lines are much too thin, even on the user preferences "thick" setting. Very difficult to see. Objects in object mode look sketchy like they were drawn in with a pencil, and when a line appears directly over a grid line, it's practically invisible. Edit mode is slightly better but the vertex squares are also light and sketchy. I have my settings set to 125% display size. The problem was even worse at 100%. The worst problem is missing objects when the left button is clicked. (All of this relates to wireframe.) There is also another issue but this could be related to my particular mouse: 99% of the time, when I press down on the wheel, the display immediately jumps from ortho to perspective mode. It is infuriating. I am CONSTANTLY hitting num pad 5 to reset ortho mode over and over and over. **Exact steps for others to reproduce the error**

Added subscriber: @CMalcheski

Added subscriber: @CMalcheski

Added subscriber: @brecht

Added subscriber: @brecht

Please provide a .blend file to reproduce the problem, and maybe a screenshot showing exactly where you click right after opening the file. We need exact steps to reproduce to ensure we are talking about the same thing.

Please provide a .blend file to reproduce the problem, and maybe a screenshot showing exactly where you click right after opening the file. We need exact steps to reproduce to ensure we are talking about the same thing.

The problem is omnipresent and requires no research to reproduce. I could dump a whole bunch of time into uploading a .BLEND file that is too large to upload, and mess around with screen shots, but it won't help. The problem occurs on all files, all the time. Click anyplace that is "busy" - not someplace with a single vertex off by itself. This is why I didn't get more specific: the problem is so obvious and so widespread, just get on a 3840 x 2160 monitor, set your user preferences to display scale 1.25, load any Blender file in the universe, and start clicking where a lot of vertices are relatively close together. no_selected.png

The problem is omnipresent and requires no research to reproduce. I could dump a whole bunch of time into uploading a .BLEND file that is too large to upload, and mess around with screen shots, but it won't help. The problem occurs on all files, all the time. Click anyplace that is "busy" - not someplace with a single vertex off by itself. This is why I didn't get more specific: the problem is so obvious and so widespread, just get on a 3840 x 2160 monitor, set your user preferences to display scale 1.25, load any Blender file in the universe, and start clicking where a lot of vertices are relatively close together. ![no_selected.png](https://archive.blender.org/developer/F5874089/no_selected.png)

I am adding something I absolutely should not be adding to a bug report: this entire version 2.8 is AWESOME, it is unbelievable, and the EEVEE engine is a miracle. Why would anybody use anything else????? Okay ... my .blend file was added to the original bug report. I drag/dropped in the wrong place, sorry. Use wireframe mode. There is a lot hidden so use alt+H to unhide it but you shouldn't have to.

I am adding something I absolutely should not be adding to a bug report: this entire version 2.8 is AWESOME, it is unbelievable, and the EEVEE engine is a miracle. Why would anybody use anything else????? Okay ... my .blend file was added to the original bug report. I drag/dropped in the wrong place, sorry. Use wireframe mode. There is a lot hidden so use alt+H to unhide it but you shouldn't have to.

Added subscriber: @moisessalvador

Added subscriber: @moisessalvador

I have a 4k monitor as well and don't have that problem. But it does behave differently to 2.7, which I understand it can be seen as a bug but it's probably a design decision. In wireframe mode, you can basically end up selecting an object by the faces even though the faces are not visible, which doesn't happen in 2.7 where it always selects the closest wire to the mouse. I don't quite understand the heuristic but it hasn't been that much of a problem for me, and to be fair, 2.8's wireframe has options to perceive the faces like the Xray slider in the shading popover.

And Im sure it has nothing to do with line thickness or resolution, have you tried changing the resolution of your OS to 720p and see what happens? If you want the lines to look less fuzzy, try putting the Xray slider to 0 in the shading popover, and the Wireframe slider to 1 in the overlays

I have a 4k monitor as well and don't have that problem. But it does behave differently to 2.7, which I understand it can be seen as a bug but it's probably a design decision. In wireframe mode, you can basically end up selecting an object by the faces even though the faces are not visible, which doesn't happen in 2.7 where it always selects the closest wire to the mouse. I don't quite understand the heuristic but it hasn't been that much of a problem for me, and to be fair, 2.8's wireframe has options to perceive the faces like the Xray slider in the shading popover. And Im sure it has nothing to do with line thickness or resolution, have you tried changing the resolution of your OS to 720p and see what happens? If you want the lines to look less fuzzy, try putting the Xray slider to 0 in the shading popover, and the Wireframe slider to 1 in the overlays

I'll try those changes. But that wasn't the primary issue - the primary issue was object / vertex / line selection.sketch.png

I'll try those changes. But that wasn't the primary issue - the primary issue was object / vertex / line selection.![sketch.png](https://archive.blender.org/developer/F5875104/sketch.png)

Added subscriber: @ZedDB

Added subscriber: @ZedDB

So did it help changing the resolution or did it stay the same?

So did it help changing the resolution or did it stay the same?
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Jacques Lucke self-assigned this 2019-03-07 14:58:22 +01:00
Member

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
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
5 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#58958
No description provided.