Box and Lasso select is extremely unreliable in Face or Edge select mode (selects non-visible faces or edges) #72842
Labels
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
11 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#72842
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86
Blender Version
Broken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-30 18:20, hash:
56ef761381
Worked: (optional)
Short description of error
Using box select is extremely unreliable while in Face select or Edge select mode (I didn't observe any problems in Vertex mode). It may end up selecting non-visible faces/edges inadvertently and with seemingly no pattern to its misbehavior or workarounds (shrinking range of the clip start/end doesn't fix it, enabling face centers doesn't fix it etc.)
This problem has existed for some time now but today I finally got fed up with it after losing several minutes of work again.
I'm using a hidpi 4k screen, using Blender's UI scaling of 1.0, and OS scaling of 2.0 in case this matters.
Exact steps for others to reproduce the error
box-select-bug.blend
Start with default .blend
Enter edit mode and Subdivide cube twice
Switch to Face select mode (or Edge select mode)
Attempt to box-select a variety of faces on the cube
Notice that more often than not, extra faces which are not visible are still selected
No selection
Selecting all visible faces with box-select
Non-visible faces being selected :(
Non-visible edges being selected :(
Added subscriber: @deadpin
#88806 was marked as duplicate of this issue
#83897 was marked as duplicate of this issue
#73666 was marked as duplicate of this issue
Added subscriber: @Stan_Pancakes
I can confirm this on Linux with a GTX980Ti and a common 1080 resolution. It does seem random though: selection works just fine from the "default" view, but can fail when the object is viewed from other positions/angles.
Video demonstration here: https://youtu.be/ePgMHqJyZf4
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Confirmed'
This also happened in Blender 2.79
Selecting faces in edit mode uses OpenGL to make a drawing that maps all faces within the rectangle.
Some pixels of faces that should be 100% occluded are still drawn. This is because these faces share a same edge as the face that occluded and the threshold between drawing and not the face is hard to distinguish.
I can't think of an efficient solution to this problem.
Added subscriber: @Jaxxtrend
The precise buffer problem is conceptual and affects many selection scenarios. For example: selection of many small poly from a far distance, selection poly in big angles of view.
Added subscriber: @Blendify
Changed status from 'Confirmed' to: 'Resolved'
This has been fixed with
3685347b41
and is the same as #63356Changed status from 'Resolved' to: 'Confirmed'
Seems to still be an issue
Added subscriber: @EVH1
Box select is extremely unreliable in Face or Edge select mode (selects non-visible faces or edges)to Box and Lasso select is extremely unreliable in Face or Edge select mode (selects non-visible faces or edges)Added subscriber: @Rongix
Removed subscriber: @Rongix
Added subscriber: @ozzkar
Added subscribers: @APEC, @PratikPB2123
Added subscriber: @GeRo
Added subscriber: @lcas
https://devtalk.blender.org/t/help-me-fix-oversensitive-drag-select/24858/3?u=lcas
Got a possible solution. Very lightweight, just make an additional bitmap that is the size of the viewport, check if it sees enough verts for any given face. Tell triangles with less than 3 verts visible to go away, quads and ngons need to see at least 4. Triangles have the occasional exception but way better than before and can be avoided usually besides. Going to do edges, should be as simple as if it can see 2 verts, it's all good.