Blender Git Commits

Layer/Depsgraph: Update depsgraph for new objects

Layer/Depsgraph: Fix selectability issues

Layer: Adding unittest for a problem with selectability evaluation

This is currently failing (and causing the object_delete test to fail). To be fixed separately

Layer: Small refactor on layer_collection_add

Buildbot: Some more twqeaks to master config

Buildbot: Update bundled vetrsion of server configuration

Merge branch 'master' into blender2.8

Buildbot: SPecial branch trickery for linux slaves

Point all submodules to master branch

This way it should be safe to use `git submodule update --remote`.

Buildbot: Some special tricks for Blender 2.8 slave

Cleanup: style

Rename circle_partial -> disk_partial

We may have a 'disk' function (not the partial version).

Fix blender player

Fix T51115: Bump node is broken when the displacement socket is used

Collada - add flag to limit precision of exported data, mainly to simplify debugging

fix: collada - do proper conversion from int to bool (as with other nearby parameters)

Add gluPartialDisk replacement (imm_draw_filled_circle_partial)

Needed for custom-manipulators branch but generally useful.

fix: T50412 - collada: Replaced precision local limit function by blender's own implementation

Cleanup: style

Blender 2.8: Hook of layer collections evaluation in DEG

This moves selectability/visibility flag flush from some hardcoded
places in the code to depsgraph. This way it is possible to simply
tag depsgraph to update those flags and rest it'll do on its own.

Using depsgraph for such flush is an overkill: those flags are fully
static and can not be animated, so it doesn't really make sense to
hook only those to depsgraph.

However, in the future we will have overrides on collections, which
ideally would need to be animatable and drivable and easiest way
to support this is to do this on depsgraph level, so it ensures
proper order of evaluation for animation and drivers. And it seems
logical to do both overrides and flags flush from depsgraph from
this point of view.

This commit also includes the evaluation of IDProperty for collections,
which basically are just another form of override. So once we implement
the other kind of overrides the flushing and collection evaluation won't
change.

Patch by Sergey Sharybin and Dalai Felinto