Force field not affecting rigid body simulation #58991

New Issue

Lucas Boutrot · 2018-12-08T01:59:16+01:00

Lucas Boutrot commented

2018-12-08 01:59:16 +01:00

System Information
Operating system: Windoxs 10
Graphics card: GeForce GTX 1060

Blender Version
Broken: 2.80, 6a4e8096973, blender2.8, 2015-12-07 18.28
Worked: 2.79

Short description of error
Adding a force field to a rigid body simulation does not change anything.

Exact steps for others to reproduce the error

Quick rigid body setup with a sphere falling on a plane
Add a "Force" force field
Start the simulation

**System Information** Operating system: Windoxs 10 Graphics card: GeForce GTX 1060 **Blender Version** Broken: 2.80, 6a4e8096973, blender2.8, 2015-12-07 18.28 Worked: 2.79 **Short description of error** Adding a force field to a rigid body simulation does not change anything. **Exact steps for others to reproduce the error** - Quick rigid body setup with a sphere falling on a plane - Add a "Force" force field - Start the simulation

blender-admin commented

2018-12-08 01:59:16 +01:00

#64493 was marked as duplicate of this issue

blender-admin commented

2018-12-08 01:59:16 +01:00

#59135 was marked as duplicate of this issue

Lucas Boutrot commented

2018-12-08 01:59:17 +01:00

Added subscriber: @thornydre

Stephen Swaney commented

2018-12-08 16:37:15 +01:00

Added subscriber: @StephenSwaney

Stephen Swaney commented

2018-12-08 16:37:15 +01:00

Please attach a .blend showing the problem.

Lucas Boutrot commented

2018-12-08 16:50:22 +01:00

Sorry about that, here is a file for 2.80:
rigi_body_2_80.blend

And the same file working in 2.79:
rigi_body_2_79.blend

Sorry about that, here is a file for 2.80: [rigi_body_2_80.blend](https://archive.blender.org/developer/F5888449/rigi_body_2_80.blend) And the same file working in 2.79: [rigi_body_2_79.blend](https://archive.blender.org/developer/F5888448/rigi_body_2_79.blend)

Stephen Swaney commented

2018-12-08 16:53:31 +01:00

Thank you!

Sergej Reich was assigned by Sebastian Parborg

2018-12-10 14:44:36 +01:00

Sebastian Parborg commented

2018-12-12 16:05:03 +01:00

Added subscriber: @Cyclic51

Sergej Reich commented

2018-12-13 12:42:42 +01:00

Added subscribers: @mont29, @Sergey

Sergej Reich commented

2018-12-13 12:42:42 +01:00

Ok, I fixed part of this in 5cc015f0ad.
However there's another regression. Changes to force fields don't mark the rigid body cache as outdated (the PTCACHE_OUTDATED flag needs to be set).
I don't think I have time to figure out how the depsgraph works to add the proper relations for that, so I think either @Sergey or @mont29 should take a look.

Ok, I fixed part of this in 5cc015f0ad05. However there's another regression. Changes to force fields don't mark the rigid body cache as outdated (the PTCACHE_OUTDATED flag needs to be set). I don't think I have time to figure out how the depsgraph works to add the proper relations for that, so I think either @Sergey or @mont29 should take a look.

Sergej Reich removed their assignment 2018-12-18 18:30:09 +01:00

Sergej Reich commented

2018-12-18 18:30:09 +01:00

Added subscriber: @sreich

Jacques Lucke commented

2019-03-21 15:56:51 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-03-21 15:56:51 +01:00

@sreich, is this still an issue?

Sergey Sharybin commented

2019-03-21 16:41:36 +01:00

I can not reproduce the issue, behavior seems to be the same in 2.79 and current master.
There was a of fixes done in the area, so probably got fixed as a part of another issue?

I can not reproduce the issue, behavior seems to be the same in 2.79 and current master. There was a of fixes done in the area, so probably got fixed as a part of another issue?

Sergej Reich commented

2019-03-21 21:11:37 +01:00

As I mentioned there is a second regression here, in that changes to the force field don't invalidate rigid body cache.
Simple way to reproduce:

Add a rigid body.
Add a force field.
Simulate a few frames.
Change force field strength and see that the rigid body cache hasn't been invalidated.

As I mentioned there is a second regression here, in that changes to the force field don't invalidate rigid body cache. Simple way to reproduce: 1. Add a rigid body. 2. Add a force field. 3. Simulate a few frames. 4. Change force field strength and see that the rigid body cache hasn't been invalidated.

Sebastian Parborg commented

2019-06-11 17:27:32 +02:00

Added subscribers: @mushroomeo, @christopher.burns, @Ekiwnox, @ZedDB

Sergey Sharybin was assigned by Sebastian Parborg

2019-06-11 17:27:47 +02:00

Alessio Monti di Sopra commented

2019-06-11 19:43:40 +02:00

Added subscriber: @a.monti

Alessio Monti di Sopra commented

2019-06-11 19:43:40 +02:00

This comment was removed by @a.monti

*This comment was removed by @a.monti*

Lucas Boutrot commented

2019-06-26 13:27:04 +02:00

Changed status from 'Open' to: 'Resolved'

Lucas Boutrot closed this issue

2019-06-26 13:27:04 +02:00

Lucas Boutrot commented

2019-06-26 13:27:49 +02:00

This task seems to be resolved

Alessio Monti di Sopra commented

2019-06-26 14:12:22 +02:00

Definitely not resolved for me..
Adding force fields or changing their parameters don't trigger cache invalidation for rigid bodies.

Changing parameters works for particles and soft bodies, but adding new force fields don't.

Definitely not resolved for me.. Adding force fields or changing their parameters don't trigger cache invalidation for rigid bodies. Changing parameters works for particles and soft bodies, but adding new force fields don't.

Sergey Sharybin commented

2019-06-26 14:38:22 +02:00

If there are still issues make a new report, with all the requested information.

Alessio Monti di Sopra commented

2019-06-26 15:21:13 +02:00

In #58991#707341, @Sergey wrote:
If there are still issues make a new report, with all the requested information.

There are already a couple merged into this one: #64493 and #59135
and also this one created yesterday: #66105

I was commenting here since @ZedDB seemed to have choosen this as the main task for the issue, I can open a new one if you want so though.

> In #58991#707341, @Sergey wrote: > If there are still issues make a new report, with all the requested information. There are already a couple merged into this one: #64493 and #59135 and also this one created yesterday: #66105 I was commenting here since @ZedDB seemed to have choosen this as the main task for the issue, I can open a new one if you want so though.

Sergey Sharybin commented

2019-06-26 15:49:18 +02:00

If your issue has already an open task there is no need to open a new one. But when a task is not fully resolved for you, or re-appeared, or anything like is totally worth opening a new task.

This helps keeping track of changes and fixes, saves time when we need to look in a history (we can easily get all relevant information from a task, without need to read an entire conversation trying to not miss any crucial detail).

If your issue has already an open task there is no need to open a new one. But when a task is not fully resolved for you, or re-appeared, or anything like is totally worth opening a new task. This helps keeping track of changes and fixes, saves time when we need to look in a history (we can easily get all relevant information from a task, without need to read an entire conversation trying to not miss any crucial detail).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Force field not affecting rigid body simulation #58991