Blender Git Commits

Quiet uninitialized mem use for blank cursor

harmless but may as well initialize.

Fix free'd memory use removing constraint

Do not allocate an XRay buffer if compositing is dnot one for offscreen
rendering.

cleanup & missing break

Cycles: Avoid over-allocation in decouple ray marching

It could have happened with really long rays and small steps.

Step size will be adjusted to the clamped number of steps in order
to preserve render result compatibility as much as possible.

We should probably reformulate this a bit, so it will give the
same looking results without step tweaks. But this new behavior
should already be much better that it was before.

Ensure BLI_stat() return value is checked.

also add function attrs on BLI_fileops to ensure they're used correctly.

Amend to previous own Fix T43684: only use hack on WIN32, and use case-insensitive comparison.

Thanks to Campbell for the headup.

Fix T38808: Re-opening an image makes absolute

Fix T43708: Wrong manipulator in individual origin

Manipulator and actual behavior were out-of-sync with a single edge selected.

BMesh: calc_manipulator_stats can only check verts

Code assumed selection wasn't correctly flushed, which we ensure now.

Tweak to new UIList bookmarks & co: extend up to ten entries before using scrollbars.

But again, what we really need to fix is UI saving for that temp area...

Cleanup: Add comment about light_p being modified in one case.

Cycles: Cleanup after recent changes

Fix T43684 (again!): Mighty Windows thinks it�??s perfectly sensible to block everyone during 5 seconds for a mere stat() call on "A:" path...

For now, just always consider those floppy entries ("A:" and "B:") as valid... sigh.

Some tweaks to last commit, this is better.

Cycles: Fix for hair transmission BSDF not returning proper label

Cleanup: Deduplicate area light sampling code.

Fix crash when rendering to offscreen OpenGL, fix scons build

Compositing works with X-Ray.

Basically, before drawing X-Rays, we now bind a second depth buffer.
After drawing XRays, we do an extra resolve pass where we overwrite the
non-XRay depth buffer in pixels where the depth is not maximum (which
means background pixel, since depth is cleared before drawing X-Ray
objects).

This ensures both scene and X-Rays keep their depth values and are ready
for compositing. Well, the odd effect due to depth discontinuities can be
expected, and X-Rays are a bit more expensive (extra buffer + resolve pass)
but at least X-Rays won't invalidate depth values anymore. Whee!

Cycles: Small tweaks for Henyey Greenstein closure code.

* Avoid duplicative fabs(g) check in sample code.
* Avoid dot product in eval code.

Helps like ~1% when Scatter Anisotropy is 0.