Blender Git Commits

Gizmo: use color fading to show depth for navigate

Previously the positive axis was always brighter,
now use bright colors which face towards the view.

Gizmo: minor fix for navigation axis color

When view aligned, the near axis was hidden,
making it seem as if the opposite axis was at the front.

Gizmo: skip text drawing w/ select for navigate

Also use struct for storing extra args.

Py API Docs: New custom shader example

Fix assert in bevel modifier with certain geometry.

This happened in in the barbershop_interior.blend benchmark file, seems
duplicate hash entries are ok for this algorithm.

Fix some templates for 2.8.

Fix (unreported) `bpy.ops.wm.read_factory_settings(use_empty=True)` crash.

`BKE_blendfile_read_make_empty()` was not preserving workspaces...

Depsgraph: suppress logs from add_relation on invalid driver variables.

Rig generators (e.g. rigify) use dummy drivers to attach extra
ID references to rigs for Append/Link. These references use
Single Property variables with empty path, which is intentionally
invalid and shouldn't produce low-level error logs from depsgraph.

The removed code would always print an error because RNAPathKey
requires a valid path to produce a non-NULL reference.

Fix assertion failure evaluating depsgraph on an empty armature.

If there are no bones, chan_array may not be allocated.

Fix T57760: Depsgraph 'object_instances' showing incorrect list of objects.

It appears that Python gets next item before using current one, which
would break our Depsgraph instance iterator (since only current item is
valid there, we use the same memory at each iteration).

Working around that with an ugly ping-pong game between two sets of
iterator data, so that previous one (C RNA-iterator-wise) remains valid
memory for Python to access to.

Fix typo in comment.

Fix T57558: Outliner displaying same object twice in some cases.

Logical flaw in `BKE_scene_objects_iterator_begin()` code (two errors
actually, wrong handling of first object of Master collection, and
missing call to `object_base_unique()` to 'register' that first object
and avoid getting it returned a second time).

Simply fixed by always calling `BKE_scene_objects_iterator_next()`
after minimal proper init, that one knows how to do the things. ;)

Py API Docs: documentation for gpu_extras.presets

Depsgraph: Remove meaningless evaluation mode

With the current implementation it only confuses logic around
checks like vewport/render subdivision levels.

If this mode is really needed for any decision making, implement
this properly.

Depsgraph: Fix missing point cache reset when physics changes

Among all the lines moved around, the general idea is quite simple.
Actually, there are two ideas implemented there.

First one, is when object itself is tagged for update, we tag its
point cache component for evaluation, which makes it so point cache
is properly reset. We do it implicitly because otherwise we'll need
to go everywhere and add explicit tag in almost all the properties.

Second thing is, we link all collider and force fields to a point
cache component using special type of link. This type of link only
allows flush if change is caused by a user update. This way reset
does not happen when change is caused due to animation, but will
properly happen when user causes indirect change to the objects
which are part of physics simulation.

Depsgraph: Remove unused operation code

Add function to query whether object has any point cache

Make object point cache iteration more generic

Currently should be no functional changes, but this will
simplify implementing some incoming logic.

Depsgraph: Cleanup, code style

Should be no functional changes.

Gizmo: get background color based on view option