February 11, 2019, 14:24 (GMT) |
February 11, 2019, 14:24 (GMT) |
Depsgraph: Use proper tag source for special case Special case of handling update tag of 0 was using wrong update source, causing unwanted point cache resets on file load. |
February 11, 2019, 14:03 (GMT) |
Fix build error on macOS after recent changes. |
Revision 48355d7 by Charlie Jolly (greasepencil-experimental, greasepencil-object, greasepencil-refactor, soc-2019-npr, temp-gpencil-eval) February 11, 2019, 13:54 (GMT) |
GP: Trim Strokes: UI Changes + Fix inner loop |
February 11, 2019, 13:50 (GMT) |
Fix: Eevee SSS not rendering as expected Remove forcing separate albedo when rendering. It was creating confusion. |
February 11, 2019, 13:38 (GMT) |
Fix T61374 : vertex not visible/selectable if it is at objects origin It was caused by Null normal if the vertex is at origin. Just add a small bias to avoid this case. |
February 11, 2019, 12:53 (GMT) |
Cleanup: avoid string copy for comparing int id's More direct and readable. |
February 11, 2019, 12:39 (GMT) |
Cycles: add animation denoising Python operator. This adds a cycles.denoise_animation operator, which denoises an animation sequence or individual file. Renders must be saved as multilayer EXR files with denoising data passes. By default file path and frame range come from the current scene, and EXR files are denoised in-place. Alternatively, a different input and/or output file path can be provided. Denoising settings come from the current view layer. Renders can be denoised again with different settings, as the original noisy image is preserved along with other passes and metadata. There is no user interface yet for this feature, that comes later. Code by Lukas with modifications by Brecht. This feature was originally developed for Tangent Animation, thanks for the support! Differential Revision: https://developer.blender.org/D3889 |
February 11, 2019, 12:37 (GMT) |
Merge branch 'blender2.7' |
February 11, 2019, 12:32 (GMT) |
Cycles: add animation denoising Python operator. This adds a cycles.denoise_animation operator, which denoises an animation sequence or individual file. Renders must be saved as multilayer EXR files with denoising data passes. By default file path and frame range come from the current scene, and EXR files are denoised in-place. Alternatively, a different input and/or output file path can be provided. Denoising settings come from the current view layer. Renders can be denoised again with different settings, as the original noisy image is preserved along with other passes and metadata. There is no user interface yet for this feature, that comes later. Code by Lukas with modifications by Brecht. This feature was originally developed for Tangent Animation, thanks for the support! |
February 11, 2019, 12:24 (GMT) |
Cleanup: split user preferences out of wm.py These operations are for handling preference related tasks so move into into a preferences file. Operators still need to be renamed. |
February 11, 2019, 11:53 (GMT) |
Cycles: refactor Blender device settings handling into own file. |
February 11, 2019, 11:50 (GMT) |
UI: show camera DOF UI for workbench engine |
February 11, 2019, 09:38 (GMT) |
Fix T61185: Missing modifiers update on changes to texture Also update relations when modifier texture changes. Basically same as rB6e00415a85a9, rBca2680aaeb1 but this time for VertexWeight modifiers Reviewers: sergey Maniphest Tasks: T61185 Differential Revision: https://developer.blender.org/D4305 |
February 11, 2019, 08:09 (GMT) |
readfile: skip negative sized thumbnails We may want to use 'TEST' BCode in the future for including data besides thumbnails. This allows negative values to be used w/o attempting to load a thumbnail. |
February 11, 2019, 06:55 (GMT) |
Cleanup: unused speaker flag |
February 11, 2019, 06:49 (GMT) |
Cleanup: RNA boolean names (use prefix conventions) |
February 11, 2019, 05:58 (GMT) |
Cleanup: move runtime vars into Camera_Runtime |
February 11, 2019, 05:50 (GMT) |
Cleanup: use "_Runtime" suffix for DNA Was done everywhere except bPoseChannel. |
February 11, 2019, 04:48 (GMT) |
Preferences: remove tweak/drag threshold distinction Currently the preferences have both tweak and drag threshold, this is confusing because most actions users would consider dragging use the 'tweak' setting. Now one drag threshold is used for both, with a maximum limit of half the button unit-size in case of dragging UI elements. |
|
|
|


Master Commits
MiikaHweb | 2003-2021