'Make Links -> Modifiers' ignores Hooks #69189

Closed
opened 2019-08-26 22:37:18 +02:00 by Konstantins Visnevskis · 11 comments

Win 7x64, Gtx580,
Ubuntu 16 x64, Intel Gma 500
Blender 2.8

Not sure it's a bug, but couldn't find any mentions of a deliberate limitation.
Copying modifiers (Make Links -> Modifiers) leaves out Hook modifiers (including for identical and data linked objects).

hook2.blend

  • Control+L to copy modifiers from active object.
  • Hook modifiers don't get copied.
Win 7x64, Gtx580, Ubuntu 16 x64, Intel Gma 500 Blender 2.8 Not sure it's a bug, but couldn't find any mentions of a deliberate limitation. Copying modifiers (Make Links -> Modifiers) leaves out Hook modifiers (including for identical and data linked objects). [hook2.blend](https://archive.blender.org/developer/F7705099/hook2.blend) - Control+L to copy modifiers from active object. - Hook modifiers don't get copied.

Added subscriber: @KonstantinsVisnevskis

Added subscriber: @KonstantinsVisnevskis

#74615 was marked as duplicate of this issue

#74615 was marked as duplicate of this issue
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-08-27 09:41:08 +02:00
Member

This is explicitly disabled in code, so would not be considered a bug.
(Since the modifier stores data specific to the mesh / vgroup this could lead to unpredictable results if just copied to other objects -- it could work in some cases but would cause confusion if it doesnt for other cases...)

There is also the the Copy Attributes Addon which generally does copy the modifier (but this skips the neccessary data mentioned above, so it is basically not usable for the hook modifier either...)

Sorry to say, but in this case the only workaround to setting this up manually is to script the workflow using python...

Will close this as not-a-bug, but feel free to comment again if issues persist...

This is explicitly disabled in code, so would not be considered a bug. (Since the modifier stores data specific to the mesh / vgroup this could lead to unpredictable results if just copied to other objects -- it could work in some cases but would cause confusion if it doesnt for other cases...) There is also the the `Copy Attributes Addon` which generally **does** copy the modifier (but this skips the neccessary data mentioned above, so it is basically not usable for the hook modifier either...) Sorry to say, but in this case the only workaround to setting this up manually is to script the workflow using python... Will close this as not-a-bug, but feel free to comment again if issues persist...

Thanks, I'll probably find a work-around, but just to give an example - in my case there are 160 objects with linked data. Although it's probably possible to do some check on whether the data is compatible, I actually wasn't expecting that due to potential nuances. But what also wasn't expected is skipping the modifier alltogether, as it could skip just the hidden vertex binding list, still removing the majority of clicking work.

Thanks, I'll probably find a work-around, but just to give an example - in my case there are 160 objects with linked data. Although it's probably possible to do some check on whether the data is compatible, I actually wasn't expecting that due to potential nuances. But what also wasn't expected is skipping the modifier alltogether, as it could skip just the hidden vertex binding list, still removing the majority of clicking work.
Member

@KonstantinsVisnevskis: if I understand correctly, try Copy Attributes Menu then:

  • enable Addon
  • select objects (making the active the one to copy hooks from)
  • Ctrl+C > Copy Modifiers
@KonstantinsVisnevskis: if I understand correctly, try `Copy Attributes Menu` then: - enable Addon - select objects (making the active the one to copy hooks from) - `Ctrl`+`C` > `Copy Modifiers`

Thank you. That indeed worked.

Thank you. That indeed worked.

Added subscriber: @SergeL

Added subscriber: @SergeL

Why not to add a warning message about it, somewhere in the menu? It really feels like software fault rather than precaution and with long modifier stacks and linked objects it is very easy to miss things like that

Why not to add a warning message about it, somewhere in the menu? It really feels like software fault rather than precaution and with long modifier stacks and linked objects it is very easy to miss things like that
Member

Added subscriber: @karja

Added subscriber: @karja
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
4 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#69189
No description provided.