Blender Git Loki

USD Import: fixed conditional statement.

Geometry Nodes Curves: Add "owns direct data" functions

Merge branch 'master' into geometry-nodes-curve-support

USD Import: revert custom data layer definitions.

Per review for D10700, removing custom data definitions originally
added for attribute import, as this change requires further
discussion and as additional work is required to complete
the implementation.

Cycles: Partial fix for the viewport passes

Blender's addon should use same constants as the PassType.

One thing which is still not working in viewport is Emission and
Background passes when there is an object with Glass shader: the
object is still shaded. The final F12 render of the Emission and
background is correct. So not immediately clear what's the issue.

Small changes for debugging.

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

Cycles: Fix threading issues in the PathTrace render cancel

The actual flow is a bit of a mystery to me, but there were cases
when `PathTrace::cancel()` was waiting for the `PathTrace::render()`
to finish, but the `render_cancel_.is_requested` was cleared so that
the render_pipeline was not quitting.

The new code seems more logical to me, but really wouldn't mind a
second pair of eyes here.

DRW: Fix debug print of error in shader lib dependency.

GPUTexture: Fix max FBO attachement in panoramic view + dof + eevee

EEVEE: Depth Of Field: Add back post process depth of field.

Pretty much identical to the previous implementation. With the exception
of a temporary noise function and some simplification of the CoC
computation. This also fixes issues with the Ortho depth of field.

Most of the files were modified to comply to new shader codestyle.

This also adds partial support of panoramic cameras (bokeh and
anamorphic is still buggy).

GPencil: Bake Armature modifier for Bezier type

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

Cycles: Improvements for the resolution divider calculation

* Do not report render and denoising time if render has been cancelled.

It is not possible to estimate full rendering time from a cancelled
state, and reporting wrong time gives the scheduler the wrong idea
about how fast render is.

* Use timing of the first sample to calculate start resolution divider.

This timing is more accurate, because in viewport is known to include
a single sample, and it resembles performance better because later on
multiple samples might be scheduled, making it seen that render is
faster.

* Add some tolerance to the desired timing, so that if the higher
resolution gives close enough timing we use higher resolution. This
solves resolution divider bouncing between two values on a boundary
values of render time (however, it does not eliminate requirement of
hysteresis to really ensure this).

Some utilities became public, so that they can be covered with the
tests. This is mainly to verify own mental math, but also to allow to
play with analytical formulas without breaking things.

Cycles: Fix wrong OpenGL context manipulation in some cases

When the BlenderSession is destructed from an initialization of a
temporary are the current active context is window, not the draw
manager.

Made it so context release/activation goes correct in this case.

Steps to reproduce an original issue:
- Compile in debug mode, so that asserts are active.
- Start Cycles viewport render.
- Hit shortcut to open file (Cmd-O / Ctrl-O).

Cycles: Stop rendering as quickly as possible

The goal is to make it so stopping viewport render will happen as quick
as possible. For example, when existing render mode or when opening a
file browser. There is no need to wait for the viewport to be uniformly
sampled in those cases.

Cycles: Fix samples scheduling on retina screens

Added missing function body.

Cavity masking now has a checkbox in the UI, instead of simply turning
itself on if the concave mask factor is > 0.

Geometry Nodes Curves: Refactor, mapping from evaluated to control points

Also include some incomplete handling of radius in the curve to mesh node.
I'm not sure how much of the changes will stick around, but the reshuffling
of virtual vs. final methods will stay, and the separated caches probably
makes sense too.