Blender Git Commits

Missed changing default arg in addon_utils.disable

Fix T44320: UV island overlap considered linked

Fixed compilation error in editor/animation/anim_markers

Fix T45149: Normal Node shows a hole in its sphere with heigh scale facs

Fix T45034: MirrorBall rendering on wrong camera axis

This was a mistake in the original code from D1079.

With the current way how direction ot mirror ball works camera should look
into negative Y direction. Corrected it in the camera matrix synchronization,
so no extra calculations are needed at the render time.

That's a bit annoying, but we'd better port it to the release branch, or
otherwise we'll end up with files created with wrong camera mapping after
2.75 release.

Fix T45148, stupid own mistake, the two functions are not the same,
shouldn't have collapsed them

Revert "Lock markers now also disallows selection of markers"

This reverts commit 37fd2628058f296153a21ad359fbcbc74e9141e5.

BGE: Fix T45110, T44174, armature animations update and mirror render.

Reveiwers:Moguri, Matpi, youle

Fix T45145, multiview selection fix not working for scaled matrices.

Multiview code already accounts for scale, do not scale frame before
multiplying with matrix.

Fix T45136, only draw edges if there's something to draw.

Cycles: Respect duplicator's object motion blur settings

The idea is to make it possible to control linked duplicated objects motion
blur from the scene file without need to do overrides on the linked object
settings. Currently only supported for dupligroup duplication and all now
if duplicator object has motion blur disabled then it'll be inherited into
all the duplicated objects.

There should be no regressions/changes in look of existing files because
objects do have motion blur enabled by default.

Fix T45144: Multi-value-edit ignored range

Fix camera stereo logic use /w regular select

Fix T45133: Crash drawing material buttons

Fix memory leak /w multi-drag over a single button

Cleanup: Get rid of some ugly magic numbers...

Fix T45135: More cleanup of extreme max values in operator properties.

INT_/FLOAT_MAX are sometimes valid choices, but most of the time more
sensible values should be used here!

Fix/Cleanup possibility to type insane values in 'add' operators options.

Our 'hard limit' values was too often max_int/float here, mis-typing could
lead to crash (or infinite hanging) of Blender, see e.g.
http://blender.stackexchange.com/questions/32790/blender-forces-computer-to-reboot-after-mistyping-extreme-value-for-resolution-i

Change defaults for planar-face tool

Cleanup: quiet warning