Blender Git Commit Log

Get rid of first bunch of ViewLayer.basact accesses

Get the active base/object through workspace or context (which gets it
through workspace again) instead.

Get workspace mode from the workspace view-layer

While this probably isn't the final solution we'll go with, it's nicer
as current one, which was basically broken. So consider this as
temporary solution.

It also allows testing how changing workspace changes mode & active
object, but only by having the workspaces use different view-layers.

Decided to remove WorkSpace.mode for now. If we need to bring it back,
we'll have to version patch it anyway.

Eevee: SSS: Add separated Albedo option.

This option prevent from automatically blurring the albedo color applied to the SSS.

While this is great for preserving details it can bleed more light onto the nearby objects since the blurring will be done on pure "white" irradiance.
This issue is to be tackled in a separate commit.

GPUFramebuffer: Bump the framebuffer attachement limit to 5 color textures

Cleanup: remove timer-like check for auto-ID-override generation.

Merge branch 'blender2.8' into id_override_static

Remove override update from DEG, simply do it on undo push.

Backgroudn set tests: Correct evaluation order

All depsgraphs are sharing same object state for now, which means doing set
scene evaluation after main scene evaluation will override all modifications
done by the main scene.

Depsgraph: Tag background scene for base flags update

When setting background object, it might pull new objects in and those objects
will not have proper flags unless on_visible_update() was called afterwards.

Merge branch 'blender2.8' into greasepencil-object

Revert "Depsgraph: Remove legacy re-scheduling code"

This reverts commit 90ff88646d4312823df0610168391ab5ad80675a.

Can not do this yet, if object is not part of graph yet it will not have entry
taq. Need some more generic solution here.

Cleanup code

Depsgraph: Allow tagging whole scene for base flags flush

Depsgraph: make it more obvious who's view layer is being updated

Depsgraph: Do log from newly base flag flush function

Depsgraph: Remove legacy re-scheduling code

Depsgraph: Fix crash when deleting object which is linked both directly and indirectly

Depsgraph: Make code a bit more robust against tagging indirectly linked objects

Depsgraph: Re-schedule pending tags after relations update

It is possible to have situation when we need to both update relations and do
some updates on random IDs. This was only done before for objects using their
recalc field. This means, every update tag which did not fit into there would
have been lost after updating relations.

Now we do some smarter re-scheduling of operations after relations are updated.

Depsgraph: Directly linked objects should be priority for base flags over set scenes