Blender Git Commits

Merge branch 'master' into temp-gpencil-bezier-stroke-type

Merge branch 'master' into temp-gpencil-bezier-stroke-type

Conflicts:
source/blender/editors/transform/transform_convert_gpencil.c

Merge branch 'master' into temp-gpencil-bezier-stroke-type

GPencil: Deduplicate gpencil_3d_point_to_screen_space

GPencil: Add vertex draw to bezier strokes

GPencil: Makes points visible but smaller

GPencil: Discard verts instead of hide

Merge branch 'temp-gpencil-bezier-stroke-type' of git.blender.org:blender into temp-gpencil-bezier-stroke-type

GPencil: Add IS_BEZT_CONTROL flag for poly points

This flags indicates that the poly point is "linked" to a bezier
control point.

GPencil: Experimental hide edit points

WIP (not compilable)

GPencil: Fix drawing for Bezier weight paint

GPencil: Return true if handles were recalcualted

GPencil: Enable cyclic stroke fitting

This was overlooked during the last refactor.

GPencil: Subdivide curve segment factor

Add a helper function to subdivide a curve segment at a specific factor

Merge branch 'master' into temp-gpencil-bezier-stroke-type

GPencil: Add find_cubic_bezier_stationary_points

This function calculates the stationary points of a bezier curve.

The new fitting implementation will use this function to determin where
to place control points so that attributes, like the thickness, can be
fitted to the curve. Since we do not have handles to control the falloff
of attributes, we have to find points of interest where our
interpolation between two points gives good results.

Merge branch 'master' into temp-gpencil-bezier-stroke-type

Fix: Deactivate audio settings when output is None

Fix: geometry nodes logs incorrect preview data

Under some circumstances, modifiers are evaluated more than once.
One time to compute the actual output geometry and another time
with `MOD_APPLY_ORCO`. This design probably has to be revisited
at some point in the context of geometry nodes. However, that would
be much more involved than a bug fix.

The issue was that during the second evaluation, the node tree is
evaluated based on a slightly different input geometry. The data
generated during the second evaluation overwrote the cached
data from the first evaluation, resulting in incorrect data that is
shown in the spreadsheet.

The fix for now is to simply not log any data in the second evaluation.

Geometry Nodes: Get attribute domain and type without allocation

Because we use virtual classes (and for other reasons), we had to do a
small allocation when simply retrieving the data type and domain of an
existing attribute. This happened quite a lot actually-- to determine
these values for result attributes.

This patch adds a simple function to retrieve this meta data without
building the virtual array. This should lower the overhead of every
attribute node, though the difference probably won't be noticible
unless a tree has very many nodes.

Differential Revision: https://developer.blender.org/D11047