Blender Git Commits

Cycles: Register split kernel functions in CPUDevice

Self-explanatory.

Still need to be exposed via the Device API, but first would be nice to
quickly double-check on it.

Merge branch 'master' into temp-gpencil-io

Merge branch 'master' into greasepencil-object

Merge branch 'master' into temp-gpencil-interpolate

Cycles: Boiler plate code for the new split kernel functions

The implementation of kernels places in the kernel/integrator folder to
make some distinction between new code being written and the existing.

Currently, all the kernels have a single KernelGlobals argument and an
empty implementation. It would be nice if there is a way to have a
minimal and standard arguments, as it simplifies things in the future.

The new "section" of code is marked as such. Not sure if it's helping
or not, but kind of feels it makes it easier to see functions which
are to be removed or, at least, re-evaluated.

The way how kernels are defined and declared follows the legacy macro,
which I'm not huge fan of, but don't feel like looking into more clear
ways of replacing them is a good time investment at this time. It is
all localized, and doesn't matter too much for the actual code of the
kernels implementation.

Merge branch 'master' into xr-actions-D9124

Fix build error on Linux / gcc

Cycles: Remove CPU split kernel declaration

Was missing in the bigger split kernel removal commit.

There are still places in the code which are `ifdef __SPLIT_KERNEL__`
and those are to be removed as well. Although they aren't really in
a way yet.

Compositor: Redesign Cryptomatte node for better usability

In the current implementation, cryptomatte passes are connected to the node
and elements are picked by using the eyedropper tool on a special pick channel.

This design has two disadvantages - both connecting all passes individually
and always having to switch to the picker channel are tedious.

With the new design, the user selects the RenderLayer or Image from which the
Cryptomatte layers are directly loaded (the type of pass is determined by an
enum). This allows the node to automatically detect all relevant passes.

Then, when using the eyedropper tool, the operator looks up the selected
coordinates from the picked Image, Node backdrop or Clip and reads the picked
object directly from the Renderlayer/Image, therefore allowing to pick in any
context (e.g. by clicking on the Combined pass in the Image Viewer).

Technically there is some loss of flexibility because the Cryptomatte pass
inputs can no longer be connected to other nodes, but since any compositing
done on them is likely to break the Cryptomatte system anyways, this isn't
really a concern in practise.

In the future, this would also allow to automatically translate values to names
by looking up the value in the associated metadata of the input, or to get a
better visualization of overlapping areas in the Pick output since we could
blend colors now that the output doesn't have to contain the exact value.

{F9502764}

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

Fixed bad merge

Removed duplicate versioning code.

Code-style: switch statement.

Cleanup: Split converToOperations in multiple methods.

Codestyle: Spelling in comments.

Code-style: reduce indentation.

Reverted wrong merge: Draw manager render result.

Code style: const + naming

Clean-up: removed comment

Moved conversion to layer prefix function to cryptomatte node.

Cleanup: use zero_v3 to clean data.