Blender Git Commits

Blender Git "master" branch commits.

Page: 3011 / 5574

December 12, 2013, 06:37 (GMT)
Mesh API: Add BKE_mesh_origindex_map_create

This API function lets original data loop over its derived data,
Use for vertex paint, replacing custom function.
December 12, 2013, 05:28 (GMT)
Code Cleanup: move mesh mapping functions into their own file/header
December 12, 2013, 05:13 (GMT)
Fix T37769: inconsistent behavior of Remove Selected From Active Group.

Add Selected to Active Group presented a menu with groups to choose from, while
this seemingly inverse operation did not and used all groups of the active
object.

Now both operators present a menu, with as first option "All Groups".
December 12, 2013, 05:09 (GMT)
Fix T37780: no languages in user preferences with SCons on Windows / Linux.

The "languages" file was not copied, probably this was not noticed earlier
because it only affects clean builds.
December 12, 2013, 04:30 (GMT)
Code Cleanup: replace global debug checks in raycast with DEBUG ifdef
December 11, 2013, 21:12 (GMT)
Add meaningful default for SimpleDeform modifier's angle prop.
December 11, 2013, 21:12 (GMT)
More updates, fixes and cleanup to install_deps.sh.

So, after hours of wild hunt, I think both CMake and Scons builds work again.
There were several small issues hiding here and there, esp. for scons.

*WARNING* the --all-static is currently officially broken (it was already quite useless in fact).
I�??m seriously considering dropping it completely, having a script compiling a chain
of static libs in a complete working way for *two* different build systems is just
too much work (static libs are *really* a nightmare at link time).

Builders who want to generate static Blender (to share it e.g.) will have to handle things by hand for now.

Main other points changed:

* Many changes to generated settings for scons (notably, I had to hack around the fact that the short ld -l
option does not work with lib names like 'Iex-2_1', which is not that surprising).
* Opencollada remains the only lib built statically (can't get it to build dyn currently).
* All other libs, even ILMBase ones, are now fully dynamic ones.
* Some general cleanup with CMake definitions of built libs.
* Git-libs do not clone again and again the repo anymore!
December 11, 2013, 16:40 (GMT)
Attempt to fix compilation against libav-0.8.9
December 11, 2013, 16:06 (GMT)
Fix T37777: layout.column_flow() not working correct with retina / DPI.
December 11, 2013, 13:33 (GMT)
UI: change how number button strings are concatenated (to easy add new suffix)
December 11, 2013, 12:28 (GMT)
Fix intersect_line_plane bug causing crash on Motion trail and other
similar potential bugs in mathutils_geometry

marking no_flip as TODO
December 11, 2013, 11:40 (GMT)
UI: Small panel tweak for Dynamic Paint UI, to save some space when color type is NONE
December 11, 2013, 11:04 (GMT)
Fix for curve pinning raising an exception
December 11, 2013, 10:32 (GMT)
Move curve's boundbox and texspace calculation out of modifier stack

There were several issues with how bounding box and texture space
are calculated:

- This was done at the same time as applying modifiers, meaning if
several objects are sharing the same curve datablock, bounding
box and texture space will be calculated multiple times.

Further, allocating bounding box wasn't safe for threading.

- Bounding box and texture space were evaluated after pre-tessellation
modifiers are applied. This means Curve-level data is actually
depends on object data, and it's really bad because different
objects could have different modifiers and this leads to
conflicts (curve's data depends on object evaluation order)
and doesn't behave in a predictable way.

This commit moves bounding box and texture space evaluation from
modifier stack to own utility functions, just like it's was done
for meshes.

This makes curve objects update thread-safe, but gives some
limitations as well. Namely, with such approach it's not so
clear how to preserve the same behavior of texture space:
before this change texture space and bounding box would match
beveled curve as accurate as possible.

Old behavior was nice for quick texturing -- in most cases you
didn't need to modify texture space at all. But texture space
was depending on render/preview settings which could easily lead
to situations, when final result would be far different from
preview one.

Now we're using CV points coordinates and their radius to approximate
the bounding box. This doesn't give the same exact texture space,
but it helps a lot keeping texture space in a nice predictable way.

We could make approximation smarter in the future, but fir now
added operator to match texture space to fully tessellated curve
called "Match Texture Space".

Review link:

https://codereview.appspot.com/15410043/

Brief description:

http://wiki.blender.org/index.php/User:Nazg-gul/GSoC-2013/Results#Curve_Texture_Space
December 11, 2013, 10:32 (GMT)
Cache limiter cleanup and small fixes

- Made code a bit less cluttered to follow
- Fixed possible deadlock when enforcing limit
and highest priority element is still referenced.
December 11, 2013, 10:27 (GMT)
User Interface: Align number buttons labels to the left, number right
December 11, 2013, 10:06 (GMT)
User Interface: add colon separator for number buttons
December 11, 2013, 09:35 (GMT)
Interface: avoid setting to drawstr in widget_draw_text
Revision c0b717b by Lukas Toenne
December 11, 2013, 08:22 (GMT)
Sanity check in node links API: Make sure a valid node exists for both
sockets passed to the nodetree.links.new function, otherwise this could
lead to invalid connections between different node trees! The
ntreeAddLink function has asserts for this, but this condition needs to
be checked in the RNA method calling it.
Revision fcdc04a by Joshua Leung
December 11, 2013, 03:19 (GMT)
Fix T37755: Autokey doesn't work for local Z-Axis in Camera view with MotionPaths enabled

The problem here was that the hack used to fix T24551 in r32863
would cause the camera to jump back to its pre-transform position
after motionpaths were recalculated. This made it seem like a keyframe
wasn't inserted by AutoKeying (even though it was).
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021