Removing Effectors (from a Collection, or deleting corresponding object) does not refresh physics, hair properly #82512

Open
opened 2020-11-08 20:39:04 +01:00 by Vyacheslav Kobozev · 7 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71

Blender Version
Broken: version: 2.83.8, branch: master, commit date: 2020-10-21 08:12, hash: 5949b796f0

Desription
Hairs do not react to force deleting.

To reproduce
Open file, delete force field object.
Hair system will keep it`s deformed shape, despite force do not exist anymore.

2020-11-08_22-34-26.mp4
late responce.blend

  • in build_effector_relations the relation is properly not built anymore, but there is no way to detect if this actually changed compared to the previous state.
    And since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no "proper" update happens.
**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71 **Blender Version** Broken: version: 2.83.8, branch: master, commit date: 2020-10-21 08:12, hash: `5949b796f0` **Desription** Hairs do not react to force deleting. **To reproduce** Open file, delete force field object. Hair system will keep it`s deformed shape, despite force do not exist anymore. [2020-11-08_22-34-26.mp4](https://archive.blender.org/developer/F9240355/2020-11-08_22-34-26.mp4) [late responce.blend](https://archive.blender.org/developer/F9240351/late_responce.blend) - in `build_effector_relations` the relation is properly **not** built anymore, but there is no way to detect if this actually changed compared to the previous state. And since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no "proper" update happens.

Added subscriber: @Vyach

Added subscriber: @Vyach

#64985 was marked as duplicate of this issue

#64985 was marked as duplicate of this issue
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscribers: @JacquesLucke, @Sergey, @lichtwerk

Added subscribers: @JacquesLucke, @Sergey, @lichtwerk
Member

This is tightly related to #64985 (Effector Collection system is not updating) (if not the same), touches #60945.

In a way, removing an object from the effectors collection or deleting said object is the same:

  • in build_effector_relations the relation is properly not built anymore, but there is no way to detect if this actually changed compared to the previous state.
    And since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no "proper" update happens.

@JacquesLucke , @Sergey: can you confirm?

This is tightly related to #64985 (Effector Collection system is not updating) (if not the same), touches #60945. In a way, removing an object from the effectors collection or deleting said object is the same: - in `build_effector_relations` the relation is properly **not** built anymore, but there is no way to detect if this actually changed compared to the previous state. And since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no "proper" update happens. @JacquesLucke , @Sergey: can you confirm?
Member

Yeah, this is a more general issue. The boolean modifier and the Point Instance node in geometry nodes are effected by it as well.

Yeah, this is a more general issue. The boolean modifier and the Point Instance node in geometry nodes are effected by it as well.
Philipp Oeser changed title from Hair system no refreshment after force delete. to Removing Effectors (from a Collection, or deleting corresponding object) does not refresh physics, hair properly 2021-01-27 16:55:25 +01:00
Member

Added subscriber: @ClemensRudolph

Added subscriber: @ClemensRudolph
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:46:27 +01:00
Philipp Oeser added the
Interest
Core
label 2023-02-10 11:09:29 +01:00
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#82512
No description provided.