Duplicating object with cloth physics resets Cloth Cache Start and End values to 1 - 250 #52963

Closed
opened 2017-09-30 23:15:41 +02:00 by jiiim · 7 comments

System Information
OSX Windows

Blender Version
Broken: 2.79 and previous

Short description of error
Duplicating an object with cloth physics resets Cloth Cache Start and End values to 1 - 250
Also using linked duplicate and "Make Links -> Modifiers" does not retain the values

Exact steps for others to reproduce the error
Create mesh object
Add a cloth physics selection via physics tab
move the Cloth Cache Start and End values or just the End value
Duplicate the object with Shift-D
View the settings on the new object

Also setting the duplicate as linked duplicate (Alt-d) and Make link (alt-l) perform the same behavior

**System Information** OSX Windows **Blender Version** Broken: 2.79 and previous **Short description of error** Duplicating an object with cloth physics resets Cloth Cache Start and End values to 1 - 250 Also using linked duplicate and "Make Links -> Modifiers" does not retain the values **Exact steps for others to reproduce the error** Create mesh object Add a cloth physics selection via physics tab move the Cloth Cache Start and End values or just the End value Duplicate the object with Shift-D View the settings on the new object Also setting the duplicate as linked duplicate (Alt-d) and Make link (alt-l) perform the same behavior
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @coffeeDrinker

Added subscriber: @coffeeDrinker

Added subscriber: @zeauro

Added subscriber: @zeauro

It is not a bug. As mentioned in report, it always worked as is. It is rather a known limitation or a badly designed feature.

When you duplicate a mesh object , some of its data may be linked but it does not apply to simulate modifiers.
New object have a new simulate modifier with a new cache specific to this object.

To use the same cache, you can group original object and re-use group instance instead of duplicating object.
Or you can bake simulation in a specific .blend and re-use cache on another .blend by using external cache option.

Unretained cache values may be an indirect way to warn the user that another object refers to another cache.
It may be perceived as an inefficient and inappropriate way to d o it. But in this case : it is a design issue, not a bug.

Development target for modifiers is to create nodes to replace modifiers stack.
https://wiki.blender.org/index.php?title=User:Lucarood/Modifier_Nodes/Proposal

When object will support a node tree containing start/end values for cache, problem will no longer exist.

It is not a bug. As mentioned in report, it always worked as is. It is rather a known limitation or a badly designed feature. When you duplicate a mesh object , some of its data may be linked but it does not apply to simulate modifiers. New object have a new simulate modifier with a new cache specific to this object. To use the same cache, you can group original object and re-use group instance instead of duplicating object. Or you can bake simulation in a specific .blend and re-use cache on another .blend by using external cache option. Unretained cache values may be an indirect way to warn the user that another object refers to another cache. It may be perceived as an inefficient and inappropriate way to d o it. But in this case : it is a design issue, not a bug. Development target for modifiers is to create nodes to replace modifiers stack. https://wiki.blender.org/index.php?title=User:Lucarood/Modifier_Nodes/Proposal When object will support a node tree containing start/end values for cache, problem will no longer exist.
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Ray molenkamp self-assigned this 2017-10-07 02:19:28 +02:00
Member

@zeauro when you triage a ticket as 'not a bug' you can archive them

@zeauro when you triage a ticket as 'not a bug' you can archive them
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#52963
No description provided.