Page MenuHome
Create Task
Maniphest T44485

Wrong Border, CTRL+LMB or RMB+Drag vertex selection in mesh edit mode
Closed, ArchivedPublic
Actions

Description

System Information
Windows 7x64 home extended rus with all autoupdates installed.
NVidia GeForce 9600 GT with 9.18.13.4144 (03.02.2015) driver version
System was reinstalled few days ago, but bug is not vanished.
There is no errors on Oracle Virtual Box vitrual machine with Windows 7x64.

Blender Version
Broken: 2.74 WINx64 2015-03-31 13:39 000dfc0
Broken: 2.74 WINx32 2015-03-31 13:39 000dfc0
Broken: 2.74.5 WINx64 2015-04-21 21:33 a8adeeb
Broken: 2.53.0 WINx64 r30581
Worked: 2.52.0 WINx64 runknown

Short description of error

  1. Border select or Ctrl+LMB select also selects some random vertexes beyond selection contour in mesh edit mode with Rendered, Material, Textured or Solid shading mode. There is no errors in Wireframe or Bounding Box shading mode.

  1. RMB+Drag vertex sometimes select and drag random vertex instead of nearest to mouse vertex. There is no errors in Wireframe or Bounding Box shading mode. Usually outer contour vertexes and vertexes on faces which is seen at an acute angle are causes error. Selection of vertexes on faces viewed from above always works fine.

Exact steps for others to reproduce the error

  1. Select by border (B) or by Ctrl+LMB vertexes in grease pensil marked area in attached .blend file.

WrongSelect.blend525 KBDownload

  1. RMB+Drag selection error is random and infrequent. I don’t know how to reproduce it reliably. Repeat RMB+StartDrag+Esc several times.

Related Objects

Event Timeline

Roman Kiselevich (RKiselevich) created this task.Apr 22 2015, 5:05 PM
Roman Kiselevich (RKiselevich) raised the priority of this task from to 90.
Roman Kiselevich (RKiselevich) updated the task description. (Show Details)
Roman Kiselevich (RKiselevich) added projects: BF Blender, Modeling.
Roman Kiselevich (RKiselevich) edited a custom field.
Roman Kiselevich (RKiselevich) added a subscriber: Roman Kiselevich (RKiselevich).
Olson Burry (olson) added a subscriber: Olson Burry (olson).Apr 23 2015, 4:44 AM

This could be due to having Multisampling enabled in the user preferences -> system -> window draw preferences, or antialiasing being forced from graphics card settings in nvidia control panel potentially - would check preferences in Blender first

Roman Kiselevich (RKiselevich) added a comment.Apr 23 2015, 6:34 AM

Yes, antialiasing 2x in standard "Balance" NVidia control panel preset was enabled.
When i switch antialiasing to "application driven", all selection errors are gone.
Thank you very much, you saved my mouse, keyboard and at least 100 meters of my nervous!

Campbell Barton (campbellbarton) changed the task status from Unknown Status to Archived.Apr 23 2015, 10:02 AM
Campbell Barton (campbellbarton) claimed this task.