Rigid Body Constraint on passive object causes dependency cycle #78952

Closed
opened 2020-07-15 17:16:43 +02:00 by RedMser · 14 comments
Contributor

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-08 20:30, hash: 31bc76ea4e
Worked: 2.79b

Short description of error
Adding a Rigid Body Constraint to a (passive) Rigid Body Object causes a dependency cycle.

I don't know if this is a big "problem" (any performance issues, breaking more complex physics setups when doing this), but considering how this setup is recommended as an alternative to using an empty object in the manual, it seems worth looking into.

Exact steps for others to reproduce the error
Load this file in Blender 2.90:
bug_depsgraph_rigidbodyconstaints.blend
For easier comparison of both methods, two pairs of objects exists. FirstC/SecondC cause the deps cycle (with FirstC having the constraint), while First/Second uses a separate empty for the constraint which works fine.

The same setup does not have any deps cycles in Blender 2.79b (did not try 2.80/81/82), see this file:
bug_depsgraph279_rigidbodyconstraints.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-08 20:30, hash: `31bc76ea4e` Worked: 2.79b **Short description of error** Adding a Rigid Body Constraint to a (passive) Rigid Body Object causes a dependency cycle. I don't know if this is a big "problem" (any performance issues, breaking more complex physics setups when doing this), but considering how this setup is [recommended as an alternative to using an empty object in the manual](https://docs.blender.org/manual/en/latest/physics/rigid_body/constraints/introduction.html#physics-menu), it seems worth looking into. **Exact steps for others to reproduce the error** Load this file in Blender 2.90: [bug_depsgraph_rigidbodyconstaints.blend](https://archive.blender.org/developer/F8697171/bug_depsgraph_rigidbodyconstaints.blend) For easier comparison of both methods, two pairs of objects exists. FirstC/SecondC cause the deps cycle (with FirstC having the constraint), while First/Second uses a separate empty for the constraint which works fine. The same setup does not have any deps cycles in Blender 2.79b (did not try 2.80/81/82), see this file: [bug_depsgraph279_rigidbodyconstraints.blend](https://archive.blender.org/developer/F8697180/bug_depsgraph279_rigidbodyconstraints.blend)
Author
Contributor

Added subscriber: @RedMser

Added subscriber: @RedMser

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I don't know if this is a big "problem" (any performance issues, breaking more complex physics setups when doing this), but considering how this setup is recommended as an alternative to using an empty object in the manual, it seems worth looking into.

Can you cite where this is suggested? I don't really see it there.

Comparison with 2.79 behavior isn't really valid, because it used old dependency graph.

>I don't know if this is a big "problem" (any performance issues, breaking more complex physics setups when doing this), but considering how this setup is recommended as an alternative to using an empty object in the manual, it seems worth looking into. Can you cite where this is suggested? I don't really see it there. Comparison with 2.79 behavior isn't really valid, because it used old dependency graph.
Author
Contributor

Can you cite where this is suggested? I don't really see it there.

See the section "Physics Menu":

"Also you can create Rigid Body Constraint on one of the two constrained objects with Rigid Body Constraint button of the Physics tab in the Properties editor. [...] This way, there are no empty object created for the constraint. The role of the empty object is put on this object. The constrained object can be then set as Passive type for better driving the constrain."

Comparison with 2.79 behavior isn't really valid, because it used old dependency graph.

Fair point. I just wanted to ensure the report wouldn't get invalidated because it didn't include any information about the "Worked" Blender version.

> Can you cite where this is suggested? I don't really see it there. See the section "Physics Menu": "Also you can create Rigid Body Constraint on one of the two constrained objects with Rigid Body Constraint button of the Physics tab in the Properties editor. [...] This way, there are no empty object created for the constraint. The role of the empty object is put on this object. The constrained object can be then set as Passive type for better driving the constrain." > Comparison with 2.79 behavior isn't really valid, because it used old dependency graph. Fair point. I just wanted to ensure the report wouldn't get invalidated because it didn't include any information about the "Worked" Blender version.

Added subscriber: @Sergey

Added subscriber: @Sergey

In #78952#979860, @RedMser wrote:

Can you cite where this is suggested? I don't really see it there.

See the section "Physics Menu":

"Also you can create Rigid Body Constraint on one of the two constrained objects with Rigid Body Constraint button of the Physics tab in the Properties editor. [...] This way, there are no empty object created for the constraint. The role of the empty object is put on this object. The constrained object can be then set as Passive type for better driving the constrain."

Perhaps I am reading this wrong(too literaly), but you haven't created constraint on "one of two constrained objects", but on unconstrained object.

I don't know much about limitations here, but when I tried to follow manual literaly, there seems to be no dependency cycle. In following file I created constraint on object Cube.
#78952.blend

But perhaps this is another bug and info in manual is outdated as well. @Sergey do you know how this should work? I can imagine this working either way really.

> In #78952#979860, @RedMser wrote: >> Can you cite where this is suggested? I don't really see it there. > > See the section "Physics Menu": > > "Also you can create Rigid Body Constraint on one of the two constrained objects with Rigid Body Constraint button of the Physics tab in the Properties editor. [...] This way, there are no empty object created for the constraint. The role of the empty object is put on this object. The constrained object can be then set as Passive type for better driving the constrain." Perhaps I am reading this wrong(too literaly), but you haven't created constraint on "one of two constrained objects", but on unconstrained object. I don't know much about limitations here, but when I tried to follow manual literaly, there seems to be no dependency cycle. In following file I created constraint on object Cube. [#78952.blend](https://archive.blender.org/developer/F8698167/T78952.blend) But perhaps this is another bug and info in manual is outdated as well. @Sergey do you know how this should work? I can imagine this working either way really.

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'

Well actually I reopened my file and there is dependecy cycle as well, so I guess ignore last comment. This means that information in manual is incorrect then.

Well actually I reopened my file and there is dependecy cycle as well, so I guess ignore last comment. This means that information in manual is incorrect then.

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

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

I have worked on another report where constraint was placed on empty which also produces dependency cycle. I think this is very likely bug so I will confirm this

I have worked on another report where constraint was placed on empty which also produces dependency cycle. I think this is very likely bug so I will confirm this
Author
Contributor

The problem has been fixed by 8dc2fbd7b6. I don't have any dependency cycles in the original blend file anymore and the constraints work as expected.

The problem has been fixed by 8dc2fbd7b6. I don't have any dependency cycles in the original blend file anymore and the constraints work as expected.

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Richard Antalik self-assigned this 2020-07-30 19:40:44 +02:00

Thanks for info. good to hear things are working

Thanks for info. good to hear things are working
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#78952
No description provided.