Blender Git Commit Log

fix attempt for disappearing fm debris particles after baking

crash fix, do not update tessface data while loading, only ensure it (saved fracture might have been invalid mesh)

Remove `BKE_boundbox_ray_hit_check`

Remove `BKE_boundbox_ray_hit_check` since it is no longer being used and can be easily replaced by `isect_ray_aabb_v3_simple`

[msvc] Set proper OpenSubdiv flags when not using find_package to find opensubdiv. Fixes T50548

New math_geom function `isect_ray_aabb_v3_simple`

The new `isect_ray_aabb_v3_simple` function replaces the `BKE_boundbox_ray_hit_check` and can be used in BVHTree Root (first AABB). So it is much more efficient.

Rename func `set_SnapData` to `snap_data_set`

Don't use CamelCase in functions and try to keep area affected first, and action last, in names

fix T50486: Don't always do the `ray_start_correction` in the ortho view

You need to make sure that ray_start is really far away, because even in the Orthografic view, in some cases, the ray can start inside the object

Remove struct `PreDefProject` and store all immutable parameters within the new struct `SnapData`

In order to simplify the reading of these functions, the parameters: `snap_to`, `mval`, `ray_start`, `ray_dir`, `view_proj` and `depth_range` are now stored in the struct `SnapData`

Fix T50550: GPUShader: compile error - Background image not showing in
viewport.

Caused by rBd6cf28c5e15739f864fbf04614c2a50708b4b152, which forgot to
update the GLSL code for the "Light Path" node.

add a space before public to follow google style

Fix blurry icons

Don't mix two operations in a single line.

* fix code style

- In Blender and C-API we follow Type *foo NOT Type* foo. Might be
different in Libmv itself.

Merge branch 'master' into soc-2016-multiview

Change in DNA/RNA. Still missing freeing and read/write.

fix D2489: Collada exporter broke edit data when exporting Armature while in Armature edit mode

fix D2489: Collada exporter broke edit data when exporting Armature while in Armature edit mode

Bring back impulse scaled repulses

It seems I was a bit too optimistic in thinking that just distance based
repulses could handle contacts nicely. Turns out impulse scaled repulses
really have enough of an influence in making the collision response more
effective, that it is worth keeping it for now, even if at the cost of a
very slight stability reduction and and a bit of an increase in
collision elasticity.

I hope to come up with a better solution, and elliminate this, after
cluster based impulse pruning is implemented.

Fix (IRC reported) DataTransfer modifier affecting base mesh in some cases.

Checking only whether mverts is same as base mesh one is not enough in
all cases, some modifiers (deform ones) can only generate new mvert
data, while keeping others from original mesh.

Now checking both mvert or medge, hopefully this will be enough to catch
all problematic cases this time.

Thanks @gaia for finding that problem. :)

Fix T50534, Part II: warn user when DataTransfer mod affects custom normals.

Custom normals need Autosmooth setting to be enabled, always!