Rigid Body Constraints Cache does not Clear #111843

Closed
opened 2023-09-03 13:15:53 +02:00 by rohan stevenson · 1 comment

System Information
Operating system: Linux-6.2.0-31-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05

Blender Version
Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a
Worked: (newest version of Blender that worked as expected)

Short description of error
Using rigid body constraints does not update its cache, even after making changes to the system leading to unexpected results.

Exact steps for others to reproduce the error

  • Playback attached blend file.
  • Note the physics is showing the linked chains as being struck by an object which is now removed from the project.
  • Making alterations or tweaking to force Blender to update the cache does not work as per this suggestion: https://www.youtube.com/watch?v=gbO1JpZCEfo
  • Changing any parameter of any participant of the simulation makes no difference.
  • Clearing unused data blocks did not work.
  • Changing the simulation speed did not work.
  • Changing links form active to passive did not work.

N.B. This situation arose because I was testing the rigid body constraints with "hinge" set to ensure they were pivoting along the correct axis. I used a simple cube animation with collision set with just 2 of the links to check the behaviour and once I was satisfied, I deleted the cube and removed the collision before duplicating the links and rigid body constraints. However, the rigid body world continued to behave as though it was being impacted by the cube. Absolutely nothing I have tried has worked to reset the cache.

**System Information** Operating system: Linux-6.2.0-31-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05 **Blender Version** Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: `e53e55951e7a` Worked: (newest version of Blender that worked as expected) **Short description of error** Using rigid body constraints does not update its cache, even after making changes to the system leading to unexpected results. **Exact steps for others to reproduce the error** - Playback attached blend file. - Note the physics is showing the linked chains as being struck by an object which is now removed from the project. - Making alterations or tweaking to force Blender to update the cache does not work as per this suggestion: https://www.youtube.com/watch?v=gbO1JpZCEfo - Changing any parameter of any participant of the simulation makes no difference. - Clearing unused data blocks did not work. - Changing the simulation speed did not work. - Changing links form active to passive did not work. N.B. This situation arose because I was testing the rigid body constraints with "hinge" set to ensure they were pivoting along the correct axis. I used a simple cube animation with collision set with just 2 of the links to check the behaviour and once I was satisfied, I deleted the cube and removed the collision before duplicating the links and rigid body constraints. However, the rigid body world continued to behave as though it was being impacted by the cube. Absolutely nothing I have tried has worked to reset the cache.
rohan stevenson added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-09-03 13:15:53 +02:00
Iliya Katushenock added the
Interest
Physics
label 2023-09-03 14:16:22 +02:00

Hi, thanks for report. As you can see in my attached video, object which is now removed from the project is not correct. Object still linked to a RigidBodyWorld collection. So this is not a bug.
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hi, thanks for report. As you can see in my attached video, `object which is now removed from the project` is not correct. Object still linked to a `RigidBodyWorld` collection. So this is not a bug. For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-09-03 19:59:23 +02: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
2 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#111843
No description provided.