Blender Git Statistics -> Branches -> blender-v2.78c-release
"Blender-v2.78c-release" branch
Total commits : 475
Total committers : 28
First Commit : September 2, 2016
Latest Commit : February 24, 2017
Commits by Month
Date | Number of Commits | |
---|---|---|
February, 2017 | 26 | |
January, 2017 | 233 | |
December, 2016 | 0 | |
November, 2016 | 0 | |
October, 2016 | 105 | |
September, 2016 | 111 |
Committers
Popular Files
Filename | Total Edits |
---|---|
deg_builder_relations.cc | 22 |
deg_builder_nodes.cc | 21 |
bvh_build.cpp | 18 |
mesh.cpp | 13 |
bvh.cpp | 12 |
properties.py | 11 |
util_math.h | 11 |
ui.py | 11 |
kernel_types.h | 11 |
blender_mesh.cpp | 10 |
Latest commits
February 24, 2017, 14:33 (GMT) |
Revert "tests: Update hash for OBJ" This changed commit was never in the release branches. Not sure why at some point CTest was expecting new hash. Probably because addons were pointing to a latest revision. This reverts commit bc27652e574a58755303442b4820620048d87615. |
February 24, 2017, 13:34 (GMT) |
Cycles: Fix compilation warning with CUDA on OSX |
February 24, 2017, 13:25 (GMT) |
Cycles: Fix non-zero exit status when rendering animation from CLI and running out of memory |
February 24, 2017, 13:20 (GMT) |
Fix Cycles still saving render output when error happened This was fixed ages ago for the interface case but not for the command line. The thing here is that currently external engines are relying on reports system to indicate that error happened so suppressing reports storage in the background mode prevented render pipeline from detecting errors happened. This is all weak and i don't like it, but this is better than delivering black frames from the farm. |
Revision bc27652 by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 17:04 (GMT) |
tests: Update hash for OBJ Was a recent update of UV precision. |
Revision 27167ee by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 16:30 (GMT) |
Cycles: Fix compilation error on 32bit Linux |
Revision 5512654 by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 16:18 (GMT) |
Fix T50243: libmv_panography_test is broken There was fully wrong logic in comparison: was actually accessing memory past the array boundary. Run test manually and the figure seems correct to me now. Spotted by @LazyDodo, thanks! |
Revision 15fb1fd by Ray molenkamp / Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 15:21 (GMT) |
[msvc] Set proper OpenSubdiv flags when not using find_package to find opensubdiv. Fixes T50548 |
Revision 7d77dcd by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 15:07 (GMT) |
Blender 2.78c: Officially move to 'c' |
Revision 909c8ec by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 14:07 (GMT) |
Cycles: Fix wrong render results with texture limit and half-float textures |
Revision b95645c by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 23, 2017, 14:07 (GMT) |
Fix T50748: Render Time incorrect when refreshing rendered preview in GPU mode |
Revision 67169e7 by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 15:58 (GMT) |
Fix T50687: Cycles baking time estimate and progress bar doesn't work / progress when baking with high samples |
Revision e89145e by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 15:48 (GMT) |
Fix T50512: Linked Backround scene with animation not updating with new depsgraph Was missing relations for the set scenes. Perhaps not ideal solution, but should be good enough for now. |
Revision dd2e33b by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 15:46 (GMT) |
Blender 2.78c: Fix crash with material preview and image sequences Don't use built-in API for image sequences since it's not really finished in RNA API. Fixes issue reported in T50616. |
Revision 99abd1f by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 15:34 (GMT) |
Blender 2.78c: Fix wrong render result with pointiness The issue was caused by pointiness being calculated after faces split now. Ported all fixes we did here. Should be safe, pointiness is used all over the barbershop. |
Revision 8ba1dab by Thomas Dinges / Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 14:33 (GMT) |
Blender 2.78c: Fix Brick Texture GLSL, broken after Mortar Smooth addition. |
Revision 9215848 by Kévin Dietrich / Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 14:25 (GMT) |
Fix T50550: GPUShader: compile error - Background image not showing in viewport. Caused by rBd6cf28c5e15739f864fbf04614c2a50708b4b152, which forgot to update the GLSL code for the "Light Path" node. |
Revision b3b4084 by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 14:08 (GMT) |
Blender 2.78c: Fix wrong cycles hair render results when using BVH motion steps This commit contains all commits required to get proper hair rendering with BVH motion steps enabled. The issue here was mainly coming from minimal pixel width feature which is quite commonly enabled in production shots. This feature will use some probabilistic heuristic in the curve intersection function to check whether we need to return intersection or not. This probability is calculated for every intersection check. Now, when we use multiple BVH nodes for curve primitives we increase probability of that primitive to be considered a good intersection for us. This is similar to increasing minimal width of curve. What is worst here is that change in the intersection probability fully depends on exact layout of BVH, meaning probability might change differently depending on a view angle, the way how builder binned the primitives and such. This makes it impossible to do simple check like dividing probability by number of BVH steps. Other solution might have been to split BVH into fully independent trees, but that will increase memory usage of all the static objects in the scenes, which is also not something desirable. For now used most simple but robust approach: store BVH primitives time and test it in curve intersection functions. This solves the regression, but has two downsides: - Uses more memory. which isn't surprising, and ANY solution to this problem will use more memory. What we still have to do is to avoid this memory increase for cases when we don't use BVH motion steps. - Reduces number of maximum available textures on pre-kepler cards. There is not much we can do here, hardware gets old but we need to move forward on more modern hardware.. |
Revision c6e4a81 by Sergey Sharybin (blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 22, 2017, 14:07 (GMT) |
Blender 2.78c: Port all commits related on new Cycles regression tests |
Revision 3c04373 by Sergey Sharybin (blender-v2.78b-release, blender-v2.78c-release, fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) February 8, 2017, 13:50 (GMT) |
Blender 2.78b: Point addons to an updated revision |
MiikaHweb - Blender Git Statistics v1.06