Blender Git Commits

Refactor mball util function, untested

I have not address MBalls directly, so there are probably other parts that are required to conform to the new code before consider than useful

Handle main object dupli functions

Missing: mesh separation, material split, mesh conversion (curve to mesh)

unittest: bpy.ops.object.duplicate

Use more of the FOREACH macros in screen_context.c

Move fricion to collider object settings

object/base iterator refactor + add FOREACH_VISIBLE_BASE

Using static for prototypes

New self collision implementation (needs some cleanup)

Fix stability issue and further make collisions inelastic

The repulse when colliding points are approaching was being scaled
incorrectly by the impulse, causing some undesired elasticity in the
collision. I imagine this was a workaround to avoid penetrations
because the collision responce was being calculated with respect to
the incorrect state, but this is no longer necessary now that that has
been fixed. (had missed this case in my previous elasticity commit)

Other than that, I have bary interpolated the static repulses to avoid a
nasty instability issue in some corner cases.

Basic Implementation of GTAO :
There is still artifacts to remove and optimisation to do.

Fix blenderplayer build

Tag areas of code that require TODO_LAYER_COPY

Merge remote-tracking branch 'origin/blender2.8' into render-layers

Manual fix: collection.c layer.c

Fix unittest for cases where we set render_layer but not scene_collection

Fix context operator test

We needed a fallback for the cases where the layer was specified but not a scene_collection

BKE_scene_layer_has_collection

Util function to check if a SceneCollection is linked to a SceneLayer

This is needed for corner cases of bpy.context.scene_collection when the context render_layer mismatches the context scene_collection.

Fix collision distance calculation (makes collisions perfectly inelastic)

Collision distance was computed with respect to the positions before the
pre-collision solve, but should rather be computed with respect to the
newly solved positions.

This fixes the issue of the collisions being semi-elastic (bouncy),
making them pretty much perfectly inelastic. This also improves the
effectiveness of the collision response, preventing penetrations even
with far less collision steps.

Left-over from previous commit (remove OBJECT_OT_move_to_layer)

Remove OBJECT_OT_move_to_layer

Link objects in scene using ObjectBase