diff options
| author | Hans Goudey <h.goudey@me.com> | 2022-06-23 20:00:25 +0300 |
|---|---|---|
| committer | Hans Goudey <h.goudey@me.com> | 2022-06-23 20:00:25 +0300 |
| commit | 54182e4925de4ee7e49e4351479e79cb257acc73 (patch) | |
| tree | d598250e653ee2e61f875b113ce4f41f87e4a084 /source/blender/blenkernel/intern/multires_reshape_apply_base.c | |
| parent | 3e5a4d14124029dd3ccb111de2db299bb405d668 (diff) | |
Mesh: Add an explicit "positions changed" function
We store various lazily calculated caches on meshes, some of which
depend on the vertex positions staying the same. The current API to
invalidate these caches is a bit confusing. With an explicit set of
functions modeled after the functions in `BKE_node_tree_update.h`,
it becomes clear which function to call. This may become more
important if more lazy caches are added in the future.
Differential Revision: https://developer.blender.org/D14760
Diffstat (limited to 'source/blender/blenkernel/intern/multires_reshape_apply_base.c')
| -rw-r--r-- | source/blender/blenkernel/intern/multires_reshape_apply_base.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blender/blenkernel/intern/multires_reshape_apply_base.c b/source/blender/blenkernel/intern/multires_reshape_apply_base.c index 837b64affa8..f7d29806353 100644 --- a/source/blender/blenkernel/intern/multires_reshape_apply_base.c +++ b/source/blender/blenkernel/intern/multires_reshape_apply_base.c @@ -156,7 +156,7 @@ void multires_reshape_apply_base_refit_base_mesh(MultiresReshapeContext *reshape /* Vertices were moved around, need to update normals after all the vertices are updated * Probably this is possible to do in the loop above, but this is rather tricky because * we don't know all needed vertices' coordinates there yet. */ - BKE_mesh_normals_tag_dirty(base_mesh); + BKE_mesh_tag_coords_changed(base_mesh); } void multires_reshape_apply_base_refine_from_base(MultiresReshapeContext *reshape_context) |