Hook seems to get double the value when using armature/bones #60563

Closed
opened 2019-01-16 14:58:13 +01:00 by Henrique Balduino Gonzaga · 8 comments

System Information
Operating system: Windows 10 64x
Graphics card: gtx 1070

Blender Version
Broken: 2.8 9390b2e645

Is doestn't matter if the order of the hook and armature modifier. it always behaves wrong.
on the video i moved the object, and then moved the bone, to show the difference.

i am not sure if it is really a bug, but it´s annoying..

Untitled Project.mp4

**System Information** Operating system: Windows 10 64x Graphics card: gtx 1070 **Blender Version** Broken: 2.8 9390b2e645a6 Is doestn't matter if the order of the hook and armature modifier. it always behaves wrong. on the video i moved the object, and then moved the bone, to show the difference. i am not sure if it is really a bug, but it´s annoying.. [Untitled Project.mp4](https://archive.blender.org/developer/F6306258/Untitled_Project.mp4)

Added subscriber: @HenriqueGonzaga

Added subscriber: @HenriqueGonzaga
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Can you prepare and update an as-simple-as-possible .blend file to showcase the bug?

Can you prepare and update an as-simple-as-possible .blend file to showcase the bug?

It looks like the hook uses global location instead of local location, and i am not sure if there is a way to change it.
If you change the hook from using the empty to use the bone, the result is the same.

hook armature.blend

It looks like the hook uses global location instead of local location, and i am not sure if there is a way to change it. If you change the hook from using the empty to use the bone, the result is the same. [hook armature.blend](https://archive.blender.org/developer/F6306510/hook_armature.blend)
Member

Ok, I see the problem. I'm just not sure if I'd consider this a bug. Could you just change the weights of the large bone so that it does not influence the vertex that is controlled by the hook?

Ok, I see the problem. I'm just not sure if I'd consider this a bug. Could you just change the weights of the large bone so that it does not influence the vertex that is controlled by the hook?
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Philipp Oeser self-assigned this 2019-01-17 10:39:18 +01:00
Member

I am also not sure what the exact usecase is here?
It is kind of expected to get double transform (one from the armature, one from the hook)
Why not just use the bone CTRL_HOOK to influence that one vertex and be done with it?

Anyways, if you really wanted a hook and separate empty object in your setup, you could:

  • parent the empty to the root bone Bone
  • constrain the bone CTRL_HOOK to the empty (and disconnect it from its parent bone)
  • make bone Bone influence all vertices except that one vertex
  • make bone CTRL_HOOK influence that one vertex

like so:
hook armature corrected.blend

I guess there are other ways to do it, too (no real rigging expert here), this is just one that first came to my mind...

Closing as "not a bug" (but feel free to comment again if issues persist)

I am also not sure what the exact usecase is here? It is kind of expected to get double transform (one from the armature, one from the hook) Why not just use the bone `CTRL_HOOK` to influence that one vertex and be done with it? Anyways, if you really wanted a hook and separate empty object in your setup, you could: - parent the empty to the root bone `Bone` - constrain the bone `CTRL_HOOK` to the empty (and disconnect it from its parent bone) - make bone `Bone` influence all vertices except that one vertex - make bone `CTRL_HOOK` influence that one vertex like so: [hook armature corrected.blend](https://archive.blender.org/developer/F6315482/hook_armature_corrected.blend) I guess there are other ways to do it, too (no real rigging expert here), this is just one that first came to my mind... Closing as "not a bug" (but feel free to comment again if issues persist)
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
No Assignees
3 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#60563
No description provided.