Blender Git Commit Log

add GVMutableArrayForVMutableArray

cleanup

cleanup

simplify

add VMutableArrayForGVMutableArray

add optional ownership

derived span

add optional ownership

add GVArrayForEmbeddedVArray

generic mutable array

LibOverride: Fix (unreported) assert when creating overrides of linked overrides.

We do not want to copy exiting overrides data from linked ID when
creating its local override (be it either a template, or because linked
ID is itself an override of another lib data).

Note that this was not a very serious issue, would just cause some memory
leak since override data is re-created on newly copied local data
anyway.

These use cases have been very little tested so far, but both complex
production pipeline and future restrictive workflow will make them fairly
common...

LibOverride: Add own flag to copy or not overrides to ID copy code.

Relying on only no-main for that was weak, and inn the end it turns out
we sometimes also need to ifnore override data during copy of Main
data-blocks.

NOTE: The new `LIB_ID_COPY_NO_LIB_OVERRIDE` is also added to the
`LIB_ID_COPY_LOCALIZE` set of flags.

NOTE: The fact that we may now copy liboverrides in some non-main cases
may cause issues in some cases, pretty impossible to track all possible
ones from reading the code... Would not expect too many problem though,
usages of `LIB_ID_CREATE_NO_MAIN` by itself are not so common.

Cycles: Correction to previous commit

Committing directly because those are rather trivial fixes for something
what got broken rather badly.

- Fix compilation error in debug mode.
- Fix non-combined passes in viewport.
- Fix adaptive sampling for final rendering.

add typed mutable virtual array

Cycles: Shorten function name

It is inside of viewport parameters, no need to repeat this in the
function name.

Cycles: Clarity comment in integrator synchronization

Cycles: Use early output and avoid over-commenting

Cycles: Move use adaptive sampling flag to integrator

Makes it closer to the rest of the adaptive sampling settings and
allows access from Scene.

The current downside is that rendering does need an extra integrator
synchronize call which will be removed by a followup development.

There should be no functional changes.

Cycles: Use range based loop

Cycles: Add idea of automatically created passes

Those are the opposite of the ones which are configured by users in the
interface.

Currently unused, preparing for taking over of automatically creating
adaptive sampling passes.