Blender Git Commits

tests: Update hash for OBJ

Was a recent update of UV precision.

Cycles: Fix compilation error on 32bit Linux

Fix T50243: libmv_panography_test is broken

There was fully wrong logic in comparison: was actually accessing memory
past the array boundary. Run test manually and the figure seems correct
to me now.

Spotted by @LazyDodo, thanks!

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

Blender 2.78c: Officially move to 'c'

Cycles: Fix wrong render results with texture limit and half-float textures

Fix T50748: Render Time incorrect when refreshing rendered preview in GPU mode

Fix T50687: Cycles baking time estimate and progress bar doesn't work / progress when baking with high samples

Fix T50512: Linked Backround scene with animation not updating with new depsgraph

Was missing relations for the set scenes.

Perhaps not ideal solution, but should be good enough for now.

Blender 2.78c: Fix crash with material preview and image sequences

Don't use built-in API for image sequences since it's not really
finished in RNA API.

Fixes issue reported in T50616.

Blender 2.78c: Fix wrong render result with pointiness

The issue was caused by pointiness being calculated after
faces split now. Ported all fixes we did here.

Should be safe, pointiness is used all over the barbershop.

Cleanup

Blender 2.78c: Fix Brick Texture GLSL, broken after Mortar Smooth addition.

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.

Blender 2.78c: Fix wrong cycles hair render results when using BVH motion steps

This commit contains all commits required to get proper hair rendering
with BVH motion steps enabled.

The issue here was mainly coming from minimal pixel width feature
which is quite commonly enabled in production shots.

This feature will use some probabilistic heuristic in the curve
intersection function to check whether we need to return intersection
or not. This probability is calculated for every intersection check.
Now, when we use multiple BVH nodes for curve primitives we increase
probability of that primitive to be considered a good intersection
for us. This is similar to increasing minimal width of curve.

What is worst here is that change in the intersection probability
fully depends on exact layout of BVH, meaning probability might
change differently depending on a view angle, the way how builder
binned the primitives and such. This makes it impossible to do
simple check like dividing probability by number of BVH steps.

Other solution might have been to split BVH into fully independent
trees, but that will increase memory usage of all the static
objects in the scenes, which is also not something desirable.

For now used most simple but robust approach: store BVH primitives
time and test it in curve intersection functions. This solves the
regression, but has two downsides:

- Uses more memory.

which isn't surprising, and ANY solution to this problem will
use more memory.

What we still have to do is to avoid this memory increase for
cases when we don't use BVH motion steps.

- Reduces number of maximum available textures on pre-kepler cards.

There is not much we can do here, hardware gets old but we need
to move forward on more modern hardware..

Blender 2.78c: Port all commits related on new Cycles regression tests

Blender 2.78b: Point addons to an updated revision

fix, keep bake until convert to keyframe has been finished, and delete then

Deleting the bake after changing the rigidbody count still is necessary, else the shard order and the mesh appearance of fracture modifier objects will be messed up.
Furthermore, decreased the convert to keyframe default threshold from 0.05 to 0.005, reconverting by re-using
the operator again still is somewhat broken

Blender release: We are officially 'b' now

[msvc] cmake fixes to support the recent for oiio/ffmpeg/numpy version changes.