Adding/removing force fields doesn't invalidate simulation caches #38442

New Issue

Y Car · 2014-02-02T01:02:31+01:00

Y Car commented

2014-02-02 01:02:31 +01:00

System Information
Ubuntu 12.04
ATI FLGRX

Blender Version
Broken: 2.69 7c9b106
Worked: never (ifaik...)

Short description of error
Force fields and Rigid bodies are not properly updated. Sometimes the order buttons are clicked does matter, and rigid bodies don't always react to force fields.
I have noticed manly 3 issues (that I name "Ghost force", "Delayed force" and "Unsensitive rigid body"), reported below.

Exact steps for others to reproduce the error

Glitchy_rb_force.blend
1°) Ghost force :

set gravitity to 0 in scene properties panel (just to better see the bug)
add a second cube (Cube.001) next to the original cube (Cube)
in Blender Render, physics properties panel, enable Force Field on 'Cube', and enable 'Rigid Body' for 'Cube.001'
run simulation (Shift+A) : all works perfectly, our rigid body moves because of the force field
disable Force field on 'Cube' => our rigid body keeps moving because of the (ghost) old force !
It seems like rigid body world is not updated when 'Force Field' is clicked on :
If you update the rigid body wold ( e.g. adding/enabeling/deleting/disabeling a rigid body), forces will act properly again.

2°) Delayed force :

set gravitity to 0 in scene properties panel (just to better see the bug)
add a second cube (Cube.001) next to the original cube (Cube)
in Blender Render, physics properties panel, enable 'Rigid Body' for 'Cube.001'
run simulation (Shift+A)
at Nth frame (where N>0), enable 'Force field' for 'Cube' => from now, rigid body will get repulsed from the force only above Nth frame (even if you run simulation again from 0th frame).

3°) Unsensitive rigid body :

set gravitity to 0 in scene properties panel (just to better see the bug)
add a second cube (Cube.001) next to the original cube (Cube)
in Blender Render, physics properties panel, enable 'Force Field' for both 'Cube' and 'Cube.001'
enable 'Rigid body' for 'Cube'
run simulation (Shift+A) => the rigid body does not move.

2°+3°bis) Unsensitive rigid body (bis) or delayed force (bis) :

set gravity to 0 in scene properties panel (just to better see the bug)
add a second cube (Cube.001) next to the original cube (Cube)
in Blender Render, physics properties panel, enable 'Force Field' for 'Cube'
enable 'Rigid body' for 'Cube.001'
enable 'Force Field' for 'Cube.001'
run simulation (Shift+A) => the rigid body DO move.
But it seems like it moves because of the '2°) Delayed Force' effect ; when you change force strength or add rigid body, Cube.001 gets stuck again.

**System Information** Ubuntu 12.04 ATI FLGRX **Blender Version** Broken: 2.69 7c9b106 Worked: never (ifaik...) **Short description of error** Force fields and Rigid bodies are not properly updated. Sometimes the order buttons are clicked does matter, and rigid bodies don't always react to force fields. I have noticed manly 3 issues (that I name "Ghost force", "Delayed force" and "Unsensitive rigid body"), reported below. **Exact steps for others to reproduce the error** [Glitchy_rb_force.blend](https://archive.blender.org/developer/F75778/Glitchy_rb_force.blend) 1°) Ghost force : - set gravitity to 0 in scene properties panel (just to better see the bug) - add a second cube (Cube.001) next to the original cube (Cube) - in Blender Render, physics properties panel, enable Force Field on 'Cube', and enable 'Rigid Body' for 'Cube.001' - run simulation (Shift+A) : all works perfectly, our rigid body moves because of the force field - disable Force field on 'Cube' => our rigid body keeps moving because of the (ghost) old force ! It seems like rigid body world is not updated when 'Force Field' is clicked on : If you update the rigid body wold ( e.g. adding/enabeling/deleting/disabeling a rigid body), forces will act properly again. 2°) Delayed force : - set gravitity to 0 in scene properties panel (just to better see the bug) - add a second cube (Cube.001) next to the original cube (Cube) - in Blender Render, physics properties panel, enable 'Rigid Body' for 'Cube.001' - run simulation (Shift+A) - at Nth frame (where N>0), enable 'Force field' for 'Cube' => from now, rigid body will get repulsed from the force only above Nth frame (even if you run simulation again from 0th frame). 3°) Unsensitive rigid body : - set gravitity to 0 in scene properties panel (just to better see the bug) - add a second cube (Cube.001) next to the original cube (Cube) - in Blender Render, physics properties panel, enable 'Force Field' for both 'Cube' and 'Cube.001' - enable 'Rigid body' for 'Cube' - run simulation (Shift+A) => the rigid body does not move. 2°+3°bis) Unsensitive rigid body (bis) or delayed force (bis) : - set gravity to 0 in scene properties panel (just to better see the bug) - add a second cube (Cube.001) next to the original cube (Cube) - in Blender Render, physics properties panel, enable 'Force Field' for 'Cube' - enable 'Rigid body' for 'Cube.001' - enable 'Force Field' for 'Cube.001' - run simulation (Shift+A) => the rigid body DO move. But it seems like it moves because of the '2°) Delayed Force' effect ; when you change force strength or add rigid body, Cube.001 gets stuck again.

Y Car commented

2014-02-02 01:02:31 +01:00

Changed status to: 'Open'

Sergey Sharybin was assigned by Y Car

2014-02-02 01:02:31 +01:00

Y Car commented

2014-02-02 01:02:31 +01:00

Added subscriber: @tchirac

Sergey Sharybin removed their assignment 2014-02-03 11:01:17 +01:00

Sergey Sharybin commented

2014-02-03 11:01:17 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-02-03 11:01:17 +01:00

No idea why it was assigned to me. I don't usually deal with rigid bodies.

Sergej Reich was assigned by Sergey Sharybin

2014-02-03 13:26:31 +01:00

Sergey Sharybin commented

2014-02-03 13:26:31 +01:00

Added subscriber: @sreich

Sergey Sharybin commented

2014-02-03 13:26:31 +01:00

On the other hand, @sreich do you mind looking into the issue? :)

Sergej Reich changed title from ~~Force fields and Rigid body uncompatibilities~~ to Adding/removing force fields doesn't invalidate simulation caches

2014-02-03 14:13:42 +01:00

Sergej Reich commented

2014-02-03 14:14:03 +01:00

it's actually a general problem with simulations, changes to force fields don't always invalidate the cache.

Sergej Reich was unassigned by Sergey Sharybin

2014-05-29 11:00:18 +02:00

Lukas Tönne was assigned by Sergey Sharybin

2014-05-29 11:00:18 +02:00

Sergey Sharybin commented

2014-05-29 11:00:18 +02:00

Lukas, remember you've been doing some changes in force fields+depsgraph. Is the issue solved now? If not, guess we'd better to move it to TODO as a part of Gooseberry project.

Lukas Tönne commented

2014-06-06 12:54:25 +02:00

Changed status from 'Open' to: 'Archived'

Lukas Tönne closed this issue

2014-06-06 12:54:25 +02:00

Lukas Tönne commented

2014-06-06 12:54:25 +02:00

Closed as a Gooseberry TODO.

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

Adding/removing force fields doesn't invalidate simulation caches #38442