Intel HD Graphics bone selection problems in edit mode/pose mode #65138

Closed
opened 4 years ago by moonshutr7 · 44 comments

Operating system: Windows 10
Graphics card: Intel HD

Broken: 2.80, f18373a9ab, master, 2019-05-25

  1. add armature - single bone
  2. go to edit mode
  3. select all
  4. subdivide bone into 2 cuts
  5. deselect all
  6. try to select bones other than the root. (can't select them or their heads)
  7. go to pose mode and the same thing happens
Operating system: Windows 10 Graphics card: Intel HD Broken: 2.80, f18373a9ab1a, master, 2019-05-25 1. add armature - single bone 2. go to edit mode 3. select all 4. subdivide bone into 2 cuts 5. deselect all 6. try to select bones other than the root. (can't select them or their heads) 7. go to pose mode and the same thing happens
Poster

Added subscriber: @moonshutr7

Added subscriber: @moonshutr7
Collaborator

#69361 was marked as duplicate of this issue

#69361 was marked as duplicate of this issue
Collaborator

#68812 was marked as duplicate of this issue

#68812 was marked as duplicate of this issue
Collaborator

#69272 was marked as duplicate of this issue

#69272 was marked as duplicate of this issue
Collaborator

#68527 was marked as duplicate of this issue

#68527 was marked as duplicate of this issue
Collaborator

#67488 was marked as duplicate of this issue

#67488 was marked as duplicate of this issue
Collaborator

#67379 was marked as duplicate of this issue

#67379 was marked as duplicate of this issue
brecht commented 4 years ago
Owner

Added subscriber: @brecht

Added subscriber: @brecht
brecht commented 4 years ago
Owner
  • Please try installing the latest graphics drivers from the Intel website if you haven't already.
  • If that doesn't help, please attach the output of Help > Save System Info, so we can see which specific Intel card and driver version is being used.
* Please try installing the latest graphics drivers from the Intel website if you haven't already. * If that doesn't help, please attach the output of Help > Save System Info, so we can see which specific Intel card and driver version is being used.
brecht commented 4 years ago
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
brecht closed this issue 4 years ago
brecht self-assigned this 4 years ago
brecht commented 4 years ago
Owner

Assuming this was fixed along with #65066 (Armature and bone selection is broken on macOS), if not we can reopen the report.

Assuming this was fixed along with #65066 (Armature and bone selection is broken on macOS), if not we can reopen the report.
Poster

Hi Brecht,

I'm still having this issue with the recent builds (after I've seen this problem was resolved in MacOS). I already updated my driver. Attached is my system info. T{F7081773}hanks

Hi Brecht, I'm still having this issue with the recent builds (after I've seen this problem was resolved in MacOS). I already updated my driver. Attached is my system info. T{[F7081773](https://archive.blender.org/developer/F7081773/system-info.txt)}hanks
brecht commented 4 years ago
Owner

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
brecht reopened this issue 4 years ago
brecht removed their assignment 4 years ago

Added subscriber: @francisco.fontes

Added subscriber: @francisco.fontes

Use Circle tool and activate bone by this addon:
https://github.com/franciscofontes/bone-activator

Use Circle tool and activate bone by this addon: https://github.com/franciscofontes/bone-activator
brecht commented 4 years ago
Owner

Added subscribers: @sineostudio, @zeauro

Added subscribers: @sineostudio, @zeauro
brecht commented 4 years ago
Owner

Added subscriber: @Rohit624

Added subscriber: @Rohit624

I have the same issue with an Intel(R) HD Graphics 4000 Intel 4.0.0 with the latest drivers installed.

I have the same issue with an Intel(R) HD Graphics 4000 Intel 4.0.0 with the latest drivers installed.

Added subscriber: @harrisSmith

Added subscriber: @harrisSmith

Exact same problem here ! Intel I3-3220, internal HD Graphics, 8GB DDR3. A work around this problem:
Display the bones in WIRE mode, then they can be selected without problems. If OCTA,ENVELOP, BOX is choosen then they CAN NOT be selected.
Other workaround this that works in POSE only: Using SHAPES ( Custom Bones ) , bones that have custom shapes can be selected. However in Edit mode there is not custom shape representation, so problem persists. Best OPTION: Display as wires and add custom bones to all bones in the armature.
Obviously this does not happen in 2.79b and before,
Regards !

Exact same problem here ! Intel I3-3220, internal HD Graphics, 8GB DDR3. A work around this problem: Display the bones in WIRE mode, then they can be selected without problems. If OCTA,ENVELOP, BOX is choosen then they CAN NOT be selected. Other workaround this that works in POSE only: Using SHAPES ( Custom Bones ) , bones that have custom shapes can be selected. However in Edit mode there is not custom shape representation, so problem persists. Best OPTION: Display as wires and add custom bones to all bones in the armature. Obviously this does not happen in 2.79b and before, Regards !
A palliative to help: https://www.youtube.com/watch?v=Ysga3NmVY6s&t=5s
brecht commented 4 years ago
Owner

This should be fixed in the 2.81 daily build I think.
https://builder.blender.org/download

This should be fixed in the 2.81 daily build I think. https://builder.blender.org/download
Collaborator

Added subscribers: @jameshollingham, @lichtwerk

Added subscribers: @jameshollingham, @lichtwerk
Collaborator

Hi everyone, I am going over bone selection reports atm. (there are a couple #68042, #66950, #67208, #69233, #68574).

Since I cannot reproduce this one (on f88022b96f), I'd like to know if this is still an issue?
Please report back so we can get bone selection sorted once and for all... thx in advance!

Hi everyone, I am going over bone selection reports atm. (there are a couple #68042, #66950, #67208, #69233, #68574). Since I cannot reproduce this one (on f88022b96f), I'd like to know if this is still an issue? Please report back so we can get bone selection sorted once and for all... thx in advance!
Poster

hi, yes it's still an issue, even on latest builds. thanks

hi, yes it's still an issue, even on latest builds. thanks
Collaborator

Added subscriber: @fclem

Added subscriber: @fclem
Collaborator

so summing up on the Intel drama, we have:

@moonshutr7 : renderer 'Intel(R) HD Graphics', vendor: 'Intel', version: '4.0.0 - Build 10.18.10.5069' (cannot tell what model that actually is...)
@harrisSmith : Intel I3-3220 (Ivy Bridge) : strictly speaking: GPU not supported (see here )
@jameshollingham : HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.4358 (Ivy Bridge) : strictly speaking: GPU not supported (see here )
@Rohit624 : intel hd graphics [no more information provided, likely unsupported GPU as well...]
@sineostudio : Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.4358 (Ivy Bridge) : strictly speaking: GPU not supported (see here )

still confused about the driver build numbers tbh, I can see 10.18.10.5069 being pretty recent, however the build numbers here https://downloadcenter.intel.com/product/80939/Graphics-Drivers are not anywhere near...
(has anyone tried the ones from the intel site?)

quoting from https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/

Intel graphics for Haswell and newer are supported and generally working well.
See the list of Intel GPUs to check which architecture your processor has.
There are a few bugs planned to be fixed still, related to selection and reflections in Eevee on specific graphics cards.

@fclem: not sure if this selection problems planned to be fixed include this reported issue here (and if that would work on these non Haswell GPUs)?
Anyways, since these GPUs are below the minimum requirements for Blender 2.80, shall we close this now...?

so summing up on the Intel drama, we have: @moonshutr7 : renderer 'Intel(R) HD Graphics', vendor: 'Intel', version: '4.0.0 - Build 10.18.10.5069' (cannot tell what model that actually is...) @harrisSmith : Intel I3-3220 (Ivy Bridge) : strictly speaking: GPU not supported (see [here ](https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/)) @jameshollingham : HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.4358 (Ivy Bridge) : strictly speaking: GPU not supported (see [here ](https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/)) @Rohit624 : intel hd graphics [no more information provided, likely unsupported GPU as well...] @sineostudio : Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.4358 (Ivy Bridge) : strictly speaking: GPU not supported (see [here ](https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/)) still confused about the driver build numbers tbh, I can see 10.18.10.5069 being pretty recent, however the build numbers here https://downloadcenter.intel.com/product/80939/Graphics-Drivers are not anywhere near... (has anyone tried the ones from the intel site?) quoting from https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ > Intel graphics for Haswell and newer are supported and generally working well. > See the list of Intel GPUs to check which architecture your processor has. > There are a few bugs planned to be fixed still, related to selection and reflections in Eevee on specific graphics cards. @fclem: not sure if this selection problems planned to be fixed include this reported issue here (and if that would work on these non Haswell GPUs)? Anyways, since these GPUs are below the minimum requirements for Blender 2.80, shall we close this now...?
lichtwerk changed title from Can't select bones in edit mode/pose mode in viewport to Intel HD Graphics bone selection problems in edit mode/pose mode 4 years ago

Added subscriber: @vignette

Added subscriber: @vignette
Collaborator

Added subscriber: @AbidMaqbool

Added subscriber: @AbidMaqbool
Collaborator

Added subscriber: @SirYo

Added subscriber: @SirYo
Collaborator

Added subscriber: @SadekMH

Added subscriber: @SadekMH
Poster

It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11).

It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11).
Poster

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
moonshutr7 closed this issue 3 years ago
moonshutr7 self-assigned this 3 years ago
Collaborator

Glad to hear, thx for reporting back...

Glad to hear, thx for reporting back...

Added subscriber: @JoyfulJourneys

Added subscriber: @JoyfulJourneys

I was having the same issue as described by the original poster. This issue was happening for me in blender 2.80 official release but is no longer happening in the later development builds for 2.81. Also, the issue is not present using 2.79, but of course, I hope I don't have to use that anymore!

Thank you for keeping blender working great! I hope this fix continues into the new official release!

I was having the same issue as described by the original poster. This issue was happening for me in blender 2.80 official release but is no longer happening in the later development builds for 2.81. Also, the issue is not present using 2.79, but of course, I hope I don't have to use that anymore! Thank you for keeping blender working great! I hope this fix continues into the new official release!
SirYo commented 3 years ago

In #65138#774295, @moonshutr7 wrote:
It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11).

how to fix sir?

> In #65138#774295, @moonshutr7 wrote: > It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11). how to fix sir?
Poster

In #65138#775938, @SirYo wrote:

In #65138#774295, @moonshutr7 wrote:
It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11).

how to fix sir?

just download latest build in https://www.blender.org/download/ - it's already fixed

> In #65138#775938, @SirYo wrote: >> In #65138#774295, @moonshutr7 wrote: >> It's already resolved (at least in my computer) in the latest 2.81 build (2019-9-11). > > how to fix sir? just download latest build in https://www.blender.org/download/ - it's already fixed

Added subscriber: @yetanotherblenderuser

Added subscriber: @yetanotherblenderuser

I just got that problem in 2.82

I have windows 10 and GTX 1060.

Tbh I don't know how I ended up witht his but right now in pose mode I can select bones only with lasso or clircle selection tool.
Previouysly it worked with any tool.

I just got that problem in 2.82 I have windows 10 and GTX 1060. Tbh I don't know how I ended up witht his but right now in pose mode I can select bones only with lasso or clircle selection tool. Previouysly it worked with any tool.
Poster

In #65138#879416, @yetanotherblenderuser wrote:
I just got that problem in 2.82

I have windows 10 and GTX 1060.

Tbh I don't know how I ended up witht his but right now in pose mode I can select bones only with lasso or clircle selection tool.
Previouysly it worked with any tool.

Are you using Intel HD?

> In #65138#879416, @yetanotherblenderuser wrote: > I just got that problem in 2.82 > > I have windows 10 and GTX 1060. > > Tbh I don't know how I ended up witht his but right now in pose mode I can select bones only with lasso or clircle selection tool. > Previouysly it worked with any tool. Are you using Intel HD?
Poster

I mean Intel CPU

I mean Intel CPU
brecht commented 3 years ago
Owner

It's most likely a different issue. If you think you found a bug, best to create a new report with example .blend file and all requested system information.
https://developer.blender.org/maniphest/task/edit/form/1/

It's most likely a different issue. If you think you found a bug, best to create a new report with example .blend file and all requested system information. https://developer.blender.org/maniphest/task/edit/form/1/

yeah it's intel cpu, the thing is I don't know how to reproduce it now :( I selected separate object and bone from armature of another object and parented it (ctrl+p).
Later, I reloaded backup file and I tried the same thing and it didn't broke bones selection, aparently there is another condition which is causing this

yeah it's intel cpu, the thing is I don't know how to reproduce it now :( I selected separate object and bone from armature of another object and parented it (ctrl+p). Later, I reloaded backup file and I tried the same thing and it didn't broke bones selection, aparently there is another condition which is causing this
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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#65138
Loading…
There is no content yet.