June 8, 2016, 19:45 (GMT) |
GP Sculpt: Make the cursor more visible on light backgrounds On light coloured backgrounds (especially on white), it was impossible to see where the cursor was. This commit adds a second ring (black) to the cursor so that on light backgrounds, even if the light ring isn't visible the black one will be. |
June 8, 2016, 19:45 (GMT) |
Hopefully fix OMP/MSVC crap... |
June 8, 2016, 19:45 (GMT) |
Dynapaint: Serious cleanup and optimization of dynamicPaint_createUVSurface (mostly). Gives 3-4% speedup in pre-bake step (from 112 to 108 seconds with own heavy test file). Note that here we have a huge potential performance boost if we replace the flat `Bounds2D *faceBB` array of UV tris bounding boxes by a real 2D AABB tree (right now, we can loop over all UV triangles times the number of pixels of the surface times 5...). |
June 8, 2016, 19:45 (GMT) |
Fix GLSL shader failing to compile on OSX Bit operations are not supported on legacy profile of OSX. |
June 8, 2016, 19:45 (GMT) |
Makefile: Use hidden FORCE target |
June 8, 2016, 19:45 (GMT) |
Support Cycles wave texture in GLSL viewport. |
June 8, 2016, 19:45 (GMT) |
Support Cycles noise texture in GLSL viewport |
June 8, 2016, 19:45 (GMT) |
Cleanup: Don't use f suffix for values in GLSL Was giving an issues in the past, will avoid it for now. |
June 8, 2016, 19:45 (GMT) |
Support voronoi texture in GLSL shading It gives some slight differences on the plane corners, but can't really figure out source of the issue here yet. It's still better than fully white texture for the previews anyway. At this point we should perhaps ifdef chunks of the code in order to have faster GLSL compilation and probably even faster compiled code. Will look into this shortly. |
June 8, 2016, 19:45 (GMT) |
Support Cycles magic texture in GLSL viewport |
June 8, 2016, 19:45 (GMT) |
Cycles: Fix long compile time with MSVC. Compile time per kernel increased alot after recent image commits, re-shuffle some code to fix this. Patch by "LazyDodo". Differential Revision: https://developer.blender.org/D2012 |
June 8, 2016, 19:45 (GMT) |
Support gradient Cycles texture in GLSL viewport |
June 8, 2016, 19:45 (GMT) |
Support Cycles brick texture in GLSL viewport |
June 8, 2016, 19:45 (GMT) |
Support Cycles's checker texture in GLSL shading |
June 8, 2016, 19:45 (GMT) |
Fix T48472: issue in array refactor, causing performance regression in BVH build. |
June 8, 2016, 19:45 (GMT) |
Fix T48470: Bendy Bones: Custom Handle References not being cleared when bone deleted In addition to the original bug report, I've gone through cleaning up a range of related bugs which only became clear when hunting around the code... * Custom Handle References weren't getting cleared when the bones they used got deleted. But, neither was the custom bone shape location/transform reference. * Various places where posebone settings are copied around were also missing code to handle the new Bendy Bone properties. (WHY DO WE HAVE SO MANY VARIATIONS OF COPYING POSE DATA!?!?) * If duplicating a Bendy Bone with custom references, and the custom references are also selected/duplicated, the new Bendy Bones will use the corresponding duplicated bones |
June 8, 2016, 19:45 (GMT) |
Add Peak Memory as render stamp option This commit adds Peak Memory to the stamp options, the value is the same one that is already shown in the image viewer. Requested by @nutel. Reviewers: campbellbarton Subscribers: campbellbarton, nutel Differential Revision: https://developer.blender.org/D1989 |
June 8, 2016, 19:45 (GMT) |
Cycles: Add XML parsing of MappingNodes to Cycles Standalone Reviewers: dingto, sergey Differential Revision: https://developer.blender.org/D2009 |
June 8, 2016, 19:45 (GMT) |
Cleanup: warnings |
June 8, 2016, 19:45 (GMT) |
Fix T48204: Generic Tablet on Linux - Erratic strokes with pressure sensitivity enabled. Once and for all - I hope! So, for the records: Xinput1 events' valuators have a first_axis and axis_count defining the 'range' of valid axes for that event - but valid data in the valuator's array **always** start at zero (which means that, if event reports first axis as being axis 2, axis 2's value is in axis_data[0]). |
|
|
|


Master Commits
MiikaHweb | 2003-2021