I mean MutableSpan<T> = ._for_witre() once instead of _for_write() in 2 or more function calls.
What the error-propagation setting of the node groups?
Function call is copy data to the stack to pass variables to the function.
Span<T>(const Span<T> values)- okay.(const T *)(T *values)- okay.(T &values)(const T &value)-…
Shouldn't attributes api cove that and just retrieve VArray with single false?\
_for_write can be non trivial, it's better to create temporary variables on the stack for all data of the geometry like points positions or handles.
Grain size can be 4096, loop body it pure vector math, also quite short. Might be even could be foreach_index_optimized<int>
I clearly do not see any usage of this thing in the PR.
To make compositor node tree totally compatible with other backends we will have to delete this at some point and just use BKE_type_conversions.hh. Same for float4 instead of ColorGeometry4f.
const float local_offset = math::abs(math::transform_point(mat, vert_positions[verts[i]]).z);
For help using Blender, please try one of the community websites: https://www.blender.org/community/
If you think you found a bug, please submit a new report and carefully follow the instruction…
- Do not doe this by using Repeat zone.
- Its just algorithmically better and more correct to use Shortest Path.
Added.
