Page MenuHome

Bone Selection with "select box " Inconsistent
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-25 19:28, hash: rB396d39c6b904
Worked: never before has this ever worked correctly.

Short description of error
When box selecting multiple bones in edit mode and they occlude each other making impossible to select all of the ones you need only allowing you to switch to other selection modes like circle select or lasso select.

Exact steps for others to reproduce the error
Open a character with multiple bones mounted onto each other.
go into edit mode
try to select a large group of bones via box select
result: some get selected some not, no matter how many times or different angles you try.

note: Lasso picks up all of them afaict
note: this also seems to work better in posemode

Here is a gif depicting the issue.

Event Timeline

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Confirmed.Sep 1 2020, 10:13 AM

Yeah, Lasso picks up all of them afaict, checking...

Well, code is quite different between lasso/box, also editmode/posemode, might no be trivial to fix.

Sybren A. Stüvel (sybren) changed the subtype of this task from "Report" to "Bug".Sep 3 2020, 5:25 PM
Sybren A. Stüvel (sybren) moved this task from Backlog to Bugs on the Animation & Rigging board.

In blender-coders this ticket might be a GPU selection issue, hence I added EEVEE & Viewport project to it.

Could be that the current example file does not show the same example as in the gif. I had to do some reverse engineering of the current functionality of box selection.

When using box selection as long as the tails and heads are selected. When both are selected the bone is selected. When a box selection does not select the tail or head of a bone, but intersects the bone the bone is selected. I did not had any issues with occluding bones. Is this an NVIDIA only issue?

Is this similar than you folks see?

I couldn't reproduce this on linux (nvidia also) so far using the example file. Perhaps it is a windows specific issue? I'm on fedora 32/AMD Ryzen 9/nvidia 2080ti


I'm in linux Mint with Nvidia ,

I think we can probably discard this bug for now, lets not close it just yet, let me ask on twitter if people experience similar issues maybe its one of those bugs where stars need to align for it to happen.

In any caseI've found it several times in different opportunities, machines, systems, and blender versions. but I also tested now again and seems like its not there anymore.
Could be an nvidia driver issue?
as i updated drivers like last week or so.

I kinda confirm this, never reported the error because I haven't been able to reproduce it consistently, but it does happen a LOT, just like @Luciano Muñoz Sessarego (looch) mentioned.

I don't know if it has to do with nvidia drivers because I experienced the same issue on computers with AMD cards too.