you cannot select bones individually #67951

Closed
opened 2019-07-30 20:57:42 +02:00 by francisco jose cabrero barranco · 36 comments

System Information
Operating system: Windows-8.1-6.3.9600 64 Bits
Graphics card: Intel(R) HD Graphics 4400 Intel 4.2.0 - Build 10.18.10.3496

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: (optional)

Short description of error
when creating a skeleton with several bones, in the pose mode, it is impossible to select individual bones without having to do it by clicking on the parent bone

Exact steps for others to reproduce the error
I created a simple three bone system with strusion, I entered the pose mode to individually select each bone and check if each one was selected, I did not get it with the left click, and with the right click the context menu of the bones opens , in the video I show the problem and the configuration of user preferences, which are the ones that are set by default{F7638022}

**System Information** Operating system: Windows-8.1-6.3.9600 64 Bits Graphics card: Intel(R) HD Graphics 4400 Intel 4.2.0 - Build 10.18.10.3496 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: (optional) **Short description of error** when creating a skeleton with several bones, in the pose mode, it is impossible to select individual bones without having to do it by clicking on the parent bone **Exact steps for others to reproduce the error** I created a simple three bone system with strusion, I entered the pose mode to individually select each bone and check if each one was selected, I did not get it with the left click, and with the right click the context menu of the bones opens , in the video I show the problem and the configuration of user preferences, which are the ones that are set by default{[F7638022](https://archive.blender.org/developer/F7638022/BUG_BONES_SELECT.mp4)}

Added subscriber: @buscavidas_producciones

Added subscriber: @buscavidas_producciones

#68217 was marked as duplicate of this issue

#68217 was marked as duplicate of this issue

#67884 was marked as duplicate of this issue

#67884 was marked as duplicate of this issue

#67910 was marked as duplicate of this issue

#67910 was marked as duplicate of this issue

#67969 was marked as duplicate of this issue

#67969 was marked as duplicate of this issue
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Could you try upgrading your GPU drivers and see if this fixes it for you?

(guess you can get them here: https://downloadcenter.intel.com/product/81497/Intel-HD-Graphics-4400)

Could you try upgrading your GPU drivers and see if this fixes it for you? (guess you can get them here: https://downloadcenter.intel.com/product/81497/Intel-HD-Graphics-4400)

Added subscribers: @Rohit624, @crmcgee2

Added subscribers: @Rohit624, @crmcgee2

Added subscriber: @CraigD

Added subscriber: @CraigD

Added subscribers: @Hooepr, @WilliamReynish

Added subscribers: @Hooepr, @WilliamReynish

Lots of reports about issues with bone selection - all seem to be from Windows users with integrated Intel graphics.

Lots of reports about issues with bone selection - all seem to be from Windows users with integrated Intel graphics.

Captura de pantalla (511).png

Captura de pantalla (510).png
Since the Alpha version I have been reviewing the driver drivers of the equipment continuously every 15 days approximately, the reason was the immediate closure of Blender when opening Cycles with shaders in preview render view, with simple objects and diffuse material, even every month or little more , I usually make a diagnosis of the state of the graphics processor, with the official Intel diagnostic tool, I imagine that you will know it, the way of working of that tool is, in addition to the analysis of the processing threads, the forced temperatures at which it works , generating for this two systems of cascading particles, in the results of the analysis it always tells me that everything is correct, updated and the maximum temerature of forced labor rarely exceeds 70º Celsius, which is not exaggerated, but something normal ... this report is the third time I have done it, both with 2.80 rc1, and with 2.80 rc2, with rc3 I did not report any p Or that I imagined that it could be solved for the stable edition, but the problem I see is difficult to identify, I see that I am not the only one who happens this, perhaps the manufacturers of these processors, when manufacturing them, did not take into account any orders of work that could receive this 4000 series of their processors, and I think that should be the problem, if I had knowledge of writing command lines, I could have tried to find the red line that generates the error, but I don't know anything about code, excuse my language, I use Google Traslate to write, I do not know English, thank you very much for the attention and patience you have with us, you are doing a spectacular job

![Captura de pantalla (511).png](https://archive.blender.org/developer/F7639235/Captura_de_pantalla__511_.png) ![Captura de pantalla (510).png](https://archive.blender.org/developer/F7639236/Captura_de_pantalla__510_.png) Since the Alpha version I have been reviewing the driver drivers of the equipment continuously every 15 days approximately, the reason was the immediate closure of Blender when opening Cycles with shaders in preview render view, with simple objects and diffuse material, even every month or little more , I usually make a diagnosis of the state of the graphics processor, with the official Intel diagnostic tool, I imagine that you will know it, the way of working of that tool is, in addition to the analysis of the processing threads, the forced temperatures at which it works , generating for this two systems of cascading particles, in the results of the analysis it always tells me that everything is correct, updated and the maximum temerature of forced labor rarely exceeds 70º Celsius, which is not exaggerated, but something normal ... this report is the third time I have done it, both with 2.80 rc1, and with 2.80 rc2, with rc3 I did not report any p Or that I imagined that it could be solved for the stable edition, but the problem I see is difficult to identify, I see that I am not the only one who happens this, perhaps the manufacturers of these processors, when manufacturing them, did not take into account any orders of work that could receive this 4000 series of their processors, and I think that should be the problem, if I had knowledge of writing command lines, I could have tried to find the red line that generates the error, but I don't know anything about code, excuse my language, I use Google Traslate to write, I do not know English, thank you very much for the attention and patience you have with us, you are doing a spectacular job
Member

Added subscribers: @fclem, @mano-wii

Added subscribers: @fclem, @mano-wii
Member

Maybe @fclem knows more? CC @mano-wii

Maybe @fclem knows more? CC @mano-wii
Germano Cavalcante self-assigned this 2019-07-31 15:57:53 +02:00

I can confirm on Windows 10 and Intel(R) HD Graphics 4000 version: 4.0.0 - Build 10.18.10.5069.

Bug introduced in 60319e25f2

I can confirm on Windows 10 and Intel(R) HD Graphics 4000 version: 4.0.0 - Build 10.18.10.5069. Bug introduced in 60319e25f2

Let me rephrase.

Is there a way I can pose bones of my model without going to the outline, and clicking the name of bones from there. I have seen other people do it in the 3d view port but I cant click any bones in pose mode from there.

Is there a way i can select the bones instead of going to the outline on the right and scrolling. As show in the picture. image.png

Let me rephrase. Is there a way I can pose bones of my model without going to the outline, and clicking the name of bones from there. I have seen other people do it in the 3d view port but I cant click any bones in pose mode from there. Is there a way i can select the bones instead of going to the outline on the right and scrolling. As show in the picture. ![image.png](https://archive.blender.org/developer/F7639673/image.png)

Updating the Intel drivers does no fix the bone selection issue.
It did resolve an issue with crashing when switching display modes.

Latest Intel® HD Graphics drivers as of today.
Driver Version10.18.10.5069
Driver Date12/27/2018

If you would like more info about my system let me know.

Updating the Intel drivers does no fix the bone selection issue. It did resolve an issue with crashing when switching display modes. Latest Intel® HD Graphics drivers as of today. Driver Version10.18.10.5069 Driver Date12/27/2018 If you would like more info about my system let me know.

is there anyway it can be fixed with the bone selection

is there anyway it can be fixed with the bone selection

There are some workarounds.

  1. Select the bone in the scene collection. This only is only good for the entire bone it does not allow for bone end movement.

  2. Using the select tool, select the root bone or its head end, then click it again to move to the next bone/head end. Doing this repeatedly will step through each bone/head. The selection order is based on how the bones are listed in the scene collection and will jump back to the root bone at the end of the bones. If you move the mouse between clicks you will have to start over. This can also be done with the move tool but the gizmo can get in the way when you do the second click. It does not work with the rotate or the transform tool because the gizmo gets in the way of the second click needed to move to the next item. You can start with the selection tool then switch tool you need when you have the bone/end selected you want to manipulate.

  3. Using the circle select tool, you can directly select the bone or end you want. This method requires some caution when selecting a bone/end. The circle select tool will select multiple bone and ends including ones that are behind the target item that are not visible. (Having X-Ray off does not change this.) The following is my work flow for this method.
    Enter Edit/Pose Mode.
    Make sure nothing is selected.
    Rotate model to be sure there is nothing hiding behind the target bone/end.
    Zoom in close to the bone/end for better selection results.
    Press c to activate the circle select tool.
    Use mouse wheel to adjust circle size, make it just big enough to get the target.
    Select the target item(s).
    Press esc to exit from the circle select tool.
    Make sure you have only the item(s) you want.
    Select the move, rotate, scale or transform and adjust as needed.

There are some workarounds. 1. Select the bone in the scene collection. This only is only good for the entire bone it does not allow for bone end movement. 2. Using the select tool, select the root bone or its head end, then click it again to move to the next bone/head end. Doing this repeatedly will step through each bone/head. The selection order is based on how the bones are listed in the scene collection and will jump back to the root bone at the end of the bones. If you move the mouse between clicks you will have to start over. This can also be done with the move tool but the gizmo can get in the way when you do the second click. It does not work with the rotate or the transform tool because the gizmo gets in the way of the second click needed to move to the next item. You can start with the selection tool then switch tool you need when you have the bone/end selected you want to manipulate. 3. Using the circle select tool, you can directly select the bone or end you want. This method requires some caution when selecting a bone/end. The circle select tool will select multiple bone and ends including ones that are behind the target item that are not visible. (Having X-Ray off does not change this.) The following is my work flow for this method. Enter Edit/Pose Mode. Make sure nothing is selected. Rotate model to be sure there is nothing hiding behind the target bone/end. Zoom in close to the bone/end for better selection results. Press c to activate the circle select tool. Use mouse wheel to adjust circle size, make it just big enough to get the target. Select the target item(s). Press esc to exit from the circle select tool. Make sure you have only the item(s) you want. Select the move, rotate, scale or transform and adjust as needed.

I detected the problem. glDrawElementsInstancedBaseVertexBaseInstance does not work well on older Intel GPUs. The last parameter (which Specifies the base instance) is completely ignored.
So the solution is to find a way to detect if this function is really supported.

I detected the problem. `glDrawElementsInstancedBaseVertexBaseInstance` does not work well on older Intel GPUs. The last parameter (which Specifies the base instance) is completely ignored. So the solution is to find a way to detect if this function is really supported.

This issue was referenced by d8fb63661b

This issue was referenced by d8fb63661b3218e536f548e763675a08221e18cd

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

can i shrink the circle to a very small bit or no?

can i shrink the circle to a very small bit or no?

Does this mean there's an actual fix, that will be in the next 2.81 development download?

Does this mean there's an actual fix, that will be in the next 2.81 development download?

Yes that’s right.

Yes that’s right.

Billreynish: Thanks for the quick response on this issue.

Hooeper: Use the mouse scroll wheel to adjust the circle tool so it is just big enough to cover the bone or the end that you want to select.

Billreynish: Thanks for the quick response on this issue. Hooeper: Use the mouse scroll wheel to adjust the circle tool so it is just big enough to cover the bone or the end that you want to select.

Added subscriber: @HirotakaImagawa

Added subscriber: @HirotakaImagawa

Will this fix for nvidia Quadro with latest driver?
If you don't think so, I prepare post as another issue with .blend to reproduce. thanks.

image.png

Will this fix for nvidia Quadro with latest driver? If you don't think so, I prepare post as another issue with .blend to reproduce. thanks. ![image.png](https://archive.blender.org/developer/F7640544/image.png)

In #67951#741522, @HirotakaImagawa wrote:
Will this fix for nvidia Quadro with latest driver?

Nothing has been changed for this GPU.
But you have to make sure it is the same bug.
And there's also the possibility that you're loading Blender with an integrated Intel GPU.
To be sure, share the generated file from Help -> Save System Info.

> In #67951#741522, @HirotakaImagawa wrote: > Will this fix for nvidia Quadro with latest driver? Nothing has been changed for this GPU. But you have to make sure it is the same bug. And there's also the possibility that you're loading Blender with an integrated Intel GPU. To be sure, share the generated file from `Help -> Save System Info`.

Thanks mano-wii. I would share the file.

system-info.txt

posted as another issue. https://developer.blender.org/T68042

Thanks mano-wii. I would share the file. [system-info.txt](https://archive.blender.org/developer/F7640597/system-info.txt) posted as another issue. https://developer.blender.org/T68042

My bone selection issue has been resolved in latest experimental build blender-2.81.0-git.d8fb63661b32-windows64.

I really enjoy using Blender and appreciate all the work that has gone into it.

Thanks to every body that has made this Blender possible.

My bone selection issue has been resolved in latest experimental build blender-2.81.0-git.d8fb63661b32-windows64. I really enjoy using Blender and appreciate all the work that has gone into it. Thanks to every body that has made this Blender possible.

Well ... I still cannot select bones with the experimental version compiled on August 1, I experience the same problem of the first report I made in its day with the official release of 2.80 on Day 30, if you need screen recording with the steps that I use from the beginning, I can make this capture, I appreciate all the time you are investing in this solution, it is not really if I can work with bones or not, but it would be strange that the next official launch did not have that repair , there are still many who use Intel 4000 series processors, maybe it's just the model of this series that my computer occupies, it's not a problem for me, I can live with it, it's just getting used to it, but others, and professionally , perhaps it will generate problems of times in their animations, by taking more time in the selection of specific bones for a pose

Well ... I still cannot select bones with the experimental version compiled on August 1, I experience the same problem of the first report I made in its day with the official release of 2.80 on Day 30, if you need screen recording with the steps that I use from the beginning, I can make this capture, I appreciate all the time you are investing in this solution, it is not really if I can work with bones or not, but it would be strange that the next official launch did not have that repair , there are still many who use Intel 4000 series processors, maybe it's just the model of this series that my computer occupies, it's not a problem for me, I can live with it, it's just getting used to it, but others, and professionally , perhaps it will generate problems of times in their animations, by taking more time in the selection of specific bones for a pose

See after the aa0322524e

See after the aa0322524e
[thanks.mp4](https://archive.blender.org/developer/F7643896/thanks.mp4)

I tried 2.81. It got worse in my environment.
image.png
hand bone can be picked only inside of red annotaion.;near by bone edge.

I tried 2.81. It got worse in my environment. ![image.png](https://archive.blender.org/developer/F7646546/image.png) hand bone can be picked only inside of red annotaion.;near by bone edge.

Added subscribers: @SirDraco65, @Mets

Added subscribers: @SirDraco65, @Mets
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
9 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#67951
No description provided.