Page MenuHome

Cannot select most bones in Blender 2.80 release
Closed, DuplicatePublic

Description

System Information
Operating system: Windows 10
Graphics card: Intel HD Graphics

Blender Version
Broken: 2.80 Release
Worked: 2.79 and earlier versions

Short description of error
Can only select the root bone of the armature using the mouse, any further bones are only selectable through the outliner or with circle select.

Exact steps for others to reproduce the error

  1. Create a new armature
  2. Extrude one bone out
  3. See if the new bone is selectable or if only the first one is able to be selected

Solutions already attempted
-Switching between right and left mouse select
-Checking and unchecking “lock object modes”
-Uninstalling and reinstalling Blender 2.8, even deleting it’s folder in AppData\Roaming\Blender Foundation\Blender\2.80

Details

Type
Bug

Event Timeline

Demeter Dzadik (Mets) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Aug 4 2019, 3:08 PM

Questions:

Has 2.80 ever not had this problem on this computer?
Could you find out your exact graphics card model? Is it an old one?
You can find 2.80 minimum requirements here: https://www.blender.org/download/requirements/

Jethro Norton (SirDraco65) raised the priority of this task from Needs Information from User to Normal.Aug 4 2019, 3:49 PM

I have never used a version of 2.8 that didn't have this issue.
Nowhere on my PC I could find my Graphics Card being referred to anything other than "Intel(R) HD Graphics". I can however confirm in the Intel Control Panel that it supports up to Open GL 4.0. It is indeed an old model, however the selection bug just seems like an oddly specific one when the rest of the viewport works at a fairly consistently high speed with little issue in other areas, only big issue being my graphics card does not seem good enough to keep up with Eevee, and crashes on use of it.

If it is simply that my PC is outdated, that is fair, and I will go back to using 2.79, but still any assistance in relation to the bug would be appreciated.

friend, I had that same problem, but in the experimental build 2.81 available, it is already fixed, as you can see in the video that you have loaded by me above, I hope my comment is useful for you too, check if you want my case , which is merged with this one of yours too and check all the steps, and the resolution achieved, a greeting