Blender Git Commits

crash fix for compound collision + expose constraint rules ui for compound mode

parts of the constraint rules can influence compound simulation behavior too, especially
clustering. You can either simulate compounds with our without triggers. First method might be slower than with constraints, but no bending. With triggers its faster, but objects always fall apart entirely (clusters can control this a bit)

disabled a verbose print when using many objects

fix for autohide with fractal (could leave holes near inner edges before); fractal/fast bisect should now also take extra objects / helper better into account

do not show dump writing routine in dump any more

did also use exception handler and manually set up signals

very simple confirm dialog whether to send crash minidump or not, with xmessage

backported existing crashpad support (win, mac, needs testing) and added breakpad support (linux)

constraint UI label / tooltip clarifications

now having Search Method, Search Limit as labels, tooltips explain that this is related to shards as well

backport of new linux library build system to FM 2.79 branch

after upgrade to Linux Mint 19 locally, nothing did work anymore basically... and in order to use this with the blender docker build system, it needed the new(er) cmake based library building system.

let neighbor shards now only be stopped if propagate trigger is enabled

added autohide filtering based on filter object vertex positions

mesh objects now use their verts and a distance, while empties (or other non-mesh objects) still
use the maximum of the object size as radius

re-enabled deform mblur for FM, and hopefully fixed related crashes

disable deform mblur in FM for now (precalced velocities)

it caused crashes at baking and rendering, as well as on saving and loading.
Needs to be re-implemented differently without customdata, rather let cycles read the rigidbody
data directly via FM.

allow grid spacing > 1

use voro particle order now correctly, fixes brick fracture problems.

fix for ghost trigger (again)

execute operator warns now if current frame is not on cache startframe

restore ghost stop trigger functionality

attempt to fix incorrect (bbox) triggering behavior

do not set edges of selected faces to sharp in external mode

because in most cases only existing objects are packed into the FM mesh, and no fracturing happens,
where you want to set fracture edges to sharp.

enable angular limit/stiffness/damping settings for plastic constraints

in fact, only forgot to uncomment