diff options
author | Sergey Sharybin <sergey.vfx@gmail.com> | 2020-01-07 15:49:42 +0300 |
---|---|---|
committer | Sergey Sharybin <sergey.vfx@gmail.com> | 2020-01-08 16:38:54 +0300 |
commit | cea67064da5fccbd400ee0c9437c9355289beab8 (patch) | |
tree | 6c98bc2e243c477643e7a58e2e22b534a856804b /tests | |
parent | 75f82d28e38f2bcfa9a261a39bbc4da82c65e7d3 (diff) |
Fix T62311: Metaball animation playback crash
This commit restores old metaball workaround which was forcing their
update from a single thread.
The root of the issue comes to the fact that metaball evaluation needs
to access metaballs from duplilists, so they are properly polygonized
with corresponding motherball which is outside of duplilist.
In a more ideal world this will be implemented in a way that will not
require iterating over all duplilists, but only through the ones which
actually contain metaballs for the given motherball. In practice this
ends up in a huge refactor in both relations builder (which meeds to
see whether there are metaballs in duplilists without actually
creating duplilist as it can not be done prior scene is evaluated)
and in metaballs area which need to use new relations information.
Additionally, metaball evaluation must become thread-safe, which is
currently not a case with dupli-object matrices. There might be issues
deeper in polygonization code which I am not aware of.
Having this forced single-thread evaluation is same as Blender 2.79
was doing.
Think it's better to have slower but simpler solution than to invest
time in refactoring area which requires deeper design changes.
Reviewed By: dfelinto
Differential Revision: https://developer.blender.org/D6539
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions