Blender Git Commits

DRW: InstanceData: Remove hacks of batch freeing callback

We instead use a handle reference counter on the GPUVertBufs used by
the instancing batches. This make sure that if an update happens on the
GPUVertBuf used to contruct the batch, they will never have the same
memory address than the previously allocated ones (since they are still
pending deletion thanks to the refcounter).

This avoid the linear search to update the GPUBatch in the case a
batch is deleted (which was even a bad option since they could be only
cleared)

GPU: Use GPU_vertbuf_create & GPU_indexbuf_calloc instead of manual alloc

GPUVertBuf: Add handle refcount

A handle refcount is here to avoid freeing of the GPUVertBuf datablock
if it is still referenced somewhere else.

This does not prevent deleting the actual data. This is to avoid too
much zombie data usage.

This is in order to avoid most hacks inside `draw_instance_data.c`.

GPUBatch: Remove most use of GPU_batch_draw_advanced()

This is in order to better encapsulate / isolate the drawing code.

Cleanup: GPUBatch: Remove GL functions from uniform assignment

Cleanup: GPUBatch: Move gpu_batch_private.h to CPP header

Cleanup: GPUShader: Remove unused code

GPUShader: Change shader state tracking to be part of the GPUContext

This remove the use of batch->program and replace it with batch->shader.

This will allow GL abstraction latter.

GPUBatch: Remove usage of gl_prim_type outside of GPU module

GPUDrawList: GL backend isolation

Fix T65148: Drivers can't access shape keys

It was impossible for drivers to use shape key properties, modifiers
generate a new mesh. After mesh evaluation the shape keys are no longer
necessary, and because of this the `key` pointer was not copied. As
drivers work on evaluated data, however, they do need this `key`
pointer.

This commit makes the `key` pointer available in evaluated meshes, but
this is somewhat dangerous. There was an explicit reason why the key on
result was kept at null pointer: to have the evaluated mesh in a
consistent state. Assigning this pointer makes it potentially
inconsistent, as the evaluated mesh and the original shape key may have
different topologies.

Reviewed By: sergey

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

Merge branch 'blender-v2.90-release'

Preferences: correct property description for keyitem restore

Spotted while checking T79657.

Reviewers: brecht

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

Fix T79743: baking still uses cage object after removal

Fix T79653: Change soft min frame start of cache from 1 to 0

It was always possible to set it to zero by typing in the value.
This new soft limit is more consistent with the fluid cache
and the Scene.frame_start property.

GPencil: Remove unused parameter and fix warning

Cleanup: incorrect comment wrapping

Missed this comment when updating fix for T77409.

Cleanup: warnings

Cleanup: spelling

Cleanup: clang-format