Blender Git Loki

simpler and cleaner reimplementation of clustering algorithm, caused crash before

Merge remote-tracking branch 'refs/remotes/origin/master' into fracture_modifier

memoryleak fix, forgot to free nor_tree in some cases

fix for messed up mesh if object is moved out of particle range, and some clarification for sub object group (last attempt to fix failed again, hrm)

fix for: comparison with wrong rigidbody count caused deactivation of the cache and simulation was not cached any more

dont use BLI_findlink for first shard (can access directly) and load shards into correct "parent" struct

crash fix when fracturing, missed initalization of listbase and quiet some warnings

replaced Shard pointer to arraypointer by ListBase for FracMesh->shard_map in DNA, for fracture modifier

forgot to calculate volume of whole object in mass calculation, leading to each shard having the same mass

Merge remote-tracking branch 'refs/remotes/origin/master' into fracture_modifier

reactivate fracture modifier object deform motionblur support, was disabled with last commit

Merge remote-tracking branch 'refs/remotes/origin/master' into fracture_modifier

Conflicts:
source/blender/editors/physics/CMakeLists.txt (reverse-merged from commit c9769a68082d334b002c449ad204de5acb93967b)

memory leak fix for text fracture / sub object groups

Merge remote-tracking branch 'refs/remotes/origin/master' into fracture_modifier

Conflicts:
source/blender/editors/physics/CMakeLists.txt

explaining comment: "need to distinguish between mesh and non-mesh objects for fracture modifier" and quiet some warnings

removed unnecessary conversion from radians to degrees (internally) and using degrees just in the UI

replaced rigidbody count function (avoiding 3 different loops over rigidbodies) and quiet some warnings

cleanup: automatic code styling with uncrustify_clean.sh

closed some memory leaks when calculating shard mass and after fracture (C++ cell struct)

added new setting for fracturing with particle sources, in most cases you want to use the particle
birth coordinates as pointsource, but you can override this to get the coordinates of the current particle simulation state. But as the particle cache is kinda broken and shows wrong positions at beginning if simulation has been run before, this can lead to errors. Best practice is to keep this option enabled, only disable if you really need to !