Blender Git Loki

Motion paths: Limit updates to changed frame range only

The idea is to only update parts of motion paths which lies between
keyframes around changed frame.

The changed frames are considered to be from second previous to
second next one to work correctly with bezier handles interpolation.

Brings updates in the Rain test animation file from around 11 sec
down to 1 sec.

Motion paths: Refactor, make update range more explicit

Allows to have a higher versatility in the API.

Should be no functional changes.

Motion paths: Cleanup, de-duplicate code

LibOverride: tweaks to custom props UI.

For now, do not allow to add custom props to overriding IDs (this should
be possible in the future, by getting basic correct behavior here is
already fairly hard, no reason to complicate things even more).

Also, properly disallow editing of existing custom props in overriding IDs.

LibOverride: Fix 'overridable' flag desapearing when setting IDProp from py code.

Do not see any reason not to copy over the flag of the old, existing
IDProp to the new one when assigning (e.g. `C.object['prop'] = 0.5`
would nuke that IDProp flag).

LibOverride: Fix several issues in handling of overridable status for IDProps.

The triple possible status of an PropertyRNA (actual C-defined prop,
py-defined IDprop behaving similar ot RNA one, or actual 'pure' custom
prop) is really confusing... Not to mention the _RNA_UI ugly thingy on
top of that. :/

Cleanup: remove override's 'static' references in some py API docs strings.

Cycles: Fix undefined behavior which can causes crashes with a misaligned address error

Cycles casts a pointer from ShaderDataTinyStorage to ShaderData, these structs by default had different alignments however (the former was 1-byte aligned, the latter 16-byte). This caused undefined behavior on at least the CUDA platform. Forcing both structs to use the same alignment fixes this.

CUDA toolkits newer than 10.1 run into this because of a compiler optimization.

Reviewed By: brecht

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

Sculpt: Cleanup, use more suitable utility function

No functional changes, just more clear semantic and shorter call.

Sculpt: Fix crash hovering mouse onto multire surface

The check around function which is only supposed to be used for
non-multires case was gone after aea8c0102ac.

Sculpt: Cleanup, grant expected usage with asserts

Don't just rely on a comment next top the code, do an assert as well.

Also, don't use `default` since that silences compiler warnings when
new enumerators are added and related code is to be verified.

More switch statements might need an adjustment, but this is something
what is easier to go over by Pablo.

Fix T69573: Driver Value does not slide along the actual value in the Driver Editor

This change is two-fold:

- Ensure the result of the F-Curve evaluation is stored on the FCurve
object. This was done in 2.79 but lost when we moved to more granular
per-curve evaluation from the depsgraph.
- Flush this result from the CoW copy back to the original.

Reviewed by: sergey

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

Fix T70236: voronoi misspelling in description

Cleanup: use const for image blending functions

Fix T70080: Newly created objects not visible with local collections

The tricky part here is to support a hidden parent and a "visible" child
collection. In this case the object should obviously be invisible. It is
all working now.

Cleanup: removed 7-year-old commented-out code marked 'for now'

Fix T70004 EEVEE: Texture Coordinate Node in world shader render artifacts

Tracking: Highlight keyframes in path visualization

This gives better idea of what's going on with your track. Example:

{F693806}

Color of keyframes are configurable from theme editor of clip editor.

Reviewers: keir, brecht, Severin

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

Fix T70202: Typo error in message

Fix T68736 EEVEE: Loose subsurface node breaks shader