Blender Git Commits

Remove subdivision hole feature.

For easier patch extraction, the code is in a separate branch.

Merge branch 'master' into geometry-nodes-level-set-nodes

Merge remote-tracking branch 'origin/master' into temp-lineart-contained

Try adding some relation on the subdivision component

Merge branch 'master' into subdivision_work

Merge branch 'master' into refactor-idprop-ui-data

Initial crappy code that doesn't do anything and wouldn't compile

* Implemented bounday/face set corner handling.
* New function SCULPT_vertex_is_corner, similar to
SCULPT_vertex_is_boundary it takes argument to
check face sets. PBVH_FACES/GRIDS version is
incomplete. It returns a bitmask of whether
the vert is a boundary corner and/or a face
set one.
* PBVH_BMESH uses a somewhat more expensive
calculation to detect corners of face set islands by
edge angle. This is currently not done for boundary
corners.

Corner pinning now happens in:

* The internal smoother dyntopo uses for stability reasons.
* SCULPT_vertex_neighbor_average_interior.
* Topology rake.
* Dyntopo collapse.

Note that DynTopo always pins face set corners
but everything else only does so if preserve face
sets is on.

Merge branch 'master' into temp-geometry-nodes-fields

Merge branch 'master' into soc-2021-curves

Merge branch 'master' into soc-2021-curve-fillet

UI: Use rounded corners for panels and subpanels

UI: Separate each choice inside radio buttons

Add some room between the choices. This way we can give the background and
non-active options the same color and make it look more like only one choice
can be active at a time.

This is in an effort to make the radio buttons and toggle buttons look different.
Currently in Blender they looked the same even though radio buttons only allow
one active option at a time, while toggles can be have multiple.

Merge branch 'temp-geometry-nodes-fields' into temp-geometry-nodes-fields--anonymous-attributes

use attribute id in more places

more uses of attribute id

initial attribute id ref

Remove accurate cryptomatte implementation

Affects both Cycles and EEVEE.

The motivation:

- For EEVEE it is a performance penalty to do GPU transfers for every
sample rendered.

- With big tile rendering in Cycles the accurate mode can have a very
high memory footprint.

- Feature parity between CPU and GPU: the GPU code paths should provide
results which are usable by production.

If there are cases when the accurate is really a must-have we'd need to
have a demo file and investigate how it can be supported on both CPU
and GPU.

Note that for comparison of accurate vs. non-accurate in the regular
Cycles should be done very carefully: CPU does not implement sorting
for non-accurate mode, so doesn't OptiX; and GPU does not support
accurate modes; CUDA doesn't implement sorting properly when adaptive
sampling is involved (what a mess!).

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

disable other link highlights

cleanup