Blender Git Commit Log

All Blender Git commits.

Page: 5166 / 8462

December 29, 2014, 08:23 (GMT)
Cycles: Disable QBVH on 32bit systems all together

The reason for this is that we don't sue SSE optimization for 32bit platforms
because of T36316.

Things to look into:

- Nail the root of the issue of that report
- Implement non-SSE traversal code for QBVH
Revision 52baf7d by Lukas Toenne
December 29, 2014, 08:14 (GMT)
Nicer doc strings for BVHTree subclasses.
Revision 817abd8 by Lukas Toenne
December 29, 2014, 08:00 (GMT)
Distinguish `use_poly_index` flag based on FACES/POLYS type instead of
an explicit argument.

This avoids meaningless cases when setting `use_poly_index` for vertex
or edge BVHs and is nicer for bmesh which does not yet support both
index types (only polys). Eventually BMeshBVHTree could support
tessfaces as well, at which point it could get a similar type enum.
December 28, 2014, 18:08 (GMT)
Fix T40930: Add a new option to select faces by smooth/flat shading.

Org code by robschia (Roberto Schiavone), first review by campbellbarton (Campbell Barton),
final review and minor changes by mont29 (Bastien Montagne).

Reviewers: cambellbarton, mont29

Subscribers: mont29, campbellbarton

Maniphest Tasks: T40930

Differential Revision: https://developer.blender.org/D638
December 28, 2014, 17:30 (GMT)
Cleanup: no need for hacks here, RNA allows for real read-only props, and if you define
a getter func, it won't rely on any DNA member either...
Revision fd18aac by Lukas Toenne
December 28, 2014, 14:48 (GMT)
Simplified dm_tessface_to_poly_index, no need to keep two version of
this around.
Revision 8e6e0af by Lukas Toenne
December 28, 2014, 14:26 (GMT)
Splitting the BVHTree python type into two distinct subclasses for
DerivedMesh and BMesh support.

This avoids messy code due to mixed data in the same py type. And makes
it clear at any point what kind of data the BVHTree instance represents.

Both types are based on the common BVHTree type, which currently does
not have any functionality of its own. Eventually it could implement
common BVH functions (find-nearest and ray casting) as well as return
read-only info about the size and type of BVH data.

Note: While the BVH functions already use callbacks for providing a
common interface in C, using this for python types would be redundant.
It also still requires specialized data for some details of testing
elements.
December 28, 2014, 11:52 (GMT)
Merge branch 'master' into asset-experiments
December 28, 2014, 11:49 (GMT)
Change timer of readdir job to 10ms, this gives an 'immediate' listing for most
usual cases, as in current master.
December 28, 2014, 05:00 (GMT)
Fix leak in cycles-bake
December 28, 2014, 05:00 (GMT)
Fix leak in select-similar regions
December 28, 2014, 05:00 (GMT)
Fix buffer overrun calculating unique names
December 28, 2014, 05:00 (GMT)
BLI_string_utf8: add BLI_strncpy_utf8_rlen
December 28, 2014, 04:13 (GMT)
cleanup: avoid ref-counting None for a new matrix
December 27, 2014, 18:38 (GMT)
Cycles: Mark visibility TODO as resolved
December 27, 2014, 18:33 (GMT)
Cycles: Fix visibility check for instanced nodes

The issue is that only instance node contains proper visibility flags,
nodes from instanced BVH are not correct.
December 27, 2014, 16:26 (GMT)
Merge branch 'master' into asset-experiments
December 27, 2014, 16:24 (GMT)
Fix a very stupid memleak in own bpy_app_translations.c code...

Safe for 2.73.
December 27, 2014, 15:21 (GMT)
crash fix: automatic material names management was wrong (got internally longer and longer and caused a stack overflow after some fracture attempts)
December 27, 2014, 14:05 (GMT)
GPencil UI: Color swatches for both Stroke and Fill colors are now shown

The layers list and the Dopesheet channels now show color swatches for both the
stroke and fill colours now. This is useful when you've got layers that only
use either/or.

* Currently, these only get shown if the relevant opacity setting is high enough
for that aspect to contribute to the result.

* The sizing of these items could do with some more tweaking (especially in the
Dopesheet), as these may now be too small to accurately see and/or interact with.

* There are some potential issues when using near-gray (or actually, colours similar
to the list backgrounds, but that issue exists in other areas of Blender anyway.


(NOTE: At this stage, these changes are still experimental, and not for 2.73 yet)
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021