Blender Git Commit Log

All Blender Git commits.

Page: 4494 / 8462

March 3, 2016, 10:11 (GMT)
Refactor BKE_copybuffer for general partial saving

Move to re-usable BKE_blendfile_write_partial API
March 3, 2016, 08:21 (GMT)
Avoid some obvious crashes when running out memory allocating render result
March 3, 2016, 08:13 (GMT)
Render Save Buffers: Use proper memory buffer size for a display buffer
March 3, 2016, 08:12 (GMT)
CMake: Remove redundant print of Git Found message

find_package(Git) will already print this.
March 3, 2016, 07:50 (GMT)
UI: move checkbox for missing add-ons to LHS
March 3, 2016, 06:34 (GMT)
Experimental option to build Blender with C11 support

It'll be nice to eventually go C11/C++11 by default, but for until
then it's kinda handy to be able to build locally with C11 support,

Reviewers: mont29, campbellbarton

Reviewed By: mont29, campbellbarton

Differential Revision: https://developer.blender.org/D1752
March 3, 2016, 02:35 (GMT)
Cleanup: take Main argument for copy
March 3, 2016, 01:36 (GMT)
Fix RNA property clamp assigning in Python

On first assignment the value was clamped, but successive assignments weren't.
March 3, 2016, 01:36 (GMT)
Cleanup: comments for creator_args & line length
March 3, 2016, 00:45 (GMT)
Armature edit-mode: Add clear-roll operator, Alt-R
March 2, 2016, 21:47 (GMT)
Increase max-frame to 500,000

Note that we could increase to 524286 without loosing subframe precision,
however this is a round number allowing for longer video export / animations.

See T46859 for details.
March 2, 2016, 19:33 (GMT)
Cleanup: replace dict /w list for module reload

Never used keys and better reload in same order loaded.
March 2, 2016, 17:12 (GMT)
Correction to own previous rB9c0de0084bfe.

'1mm+1m' would fail with original fix, now consuming all alpha chars before checking unit again...
March 2, 2016, 17:04 (GMT)
Fix bplayer (c)

Seriously...
March 2, 2016, 17:02 (GMT)
Fix T47661: cm (centimeter) unit breaks m (meter) unit in Metric.

`m` unit when used after `cm`/`mm`/etc. ones would get ignored, and the alt version of miles
would be used instead.

The root of the issue is that, in `unit_find_str`, once we get a 'hit' for a unit, we check
it's actual unit (since 'm' would also hit on 'cm', 'mm', etc.). In case that hit is not a
valid unit one, we would just return NULL, breaking the cycle of checks over that unit, and
hence missing all later usages of it.

So now, in case we have an 'invalid unit hit', we immediately retry to find it within remaining string.
March 2, 2016, 12:58 (GMT)
Fix crash accessing nodes search menu

Was caused by d49985c.
March 2, 2016, 12:58 (GMT)
Avoid node tree update tag when changed nodes which are not affecting result

This was we don't have re-compo or viewport re-rendering happening when changing
nodes which are not connected to the output at all (for example when adding new
nodes or changing settings for unconnected nodes).

Only basic operations are covered for now. checks could be added to more tools
when needed.

Currently it's not fully optimal implementation, but seems to work fast enough.
Don't see reliable alternative to that -- keeping tag in the node wouldn't work
because of the node groups (which are probably already broken, but should be
easy to solve with current approach). So guess it's more matter of optimizing
path search from a node to output.

Before processing forward let's check whether it's indeed something we want
and whether the approach is indeed not fully bad.

Reviewers: campbellbarton, mont29

Subscribers: sebastian_k

Differential Revision: https://developer.blender.org/D1765
March 2, 2016, 11:21 (GMT)
Fix T47564: Unwrapping the same mesh results in different UVs.

Pointers of faces were passed as face keys during parametrizer's face creation. Since those
addresses were different for every run, the layout of the faces ended up being different
in the internal hash, leading to inconsistent order of their evaluation during LSCM solving,
and slightly different UV maps.

Solved by simply using faces' indices as key instead, which ensures we always get same results
with exact same input data now.

Many thanks to Roman Nagornov (RomanN) for raising the issue, investigating it and finding
the solution! And thanks to Brecht for quick review too.
March 2, 2016, 10:06 (GMT)
Fix bplayer (c)
March 2, 2016, 09:53 (GMT)
Cycles: Fix wrong default value for volume samples
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021