January 30, 2019, 17:36 (GMT) |
Cleanup: use better names for depsgraph driver relations. Both the driven properties and driver targets were called targets, now make a distinction. |
Revision 53586f3 by Antonio Vazquez (greasepencil-experimental, greasepencil-object, greasepencil-refactor, soc-2019-npr, temp-gpencil-eval) January 30, 2019, 15:36 (GMT) |
Merge branch 'master' into greasepencil-object |
January 30, 2019, 15:29 (GMT) |
GP: Remove DEG_get_original_id() from draw manager Only keep this function when drawing to avoid COW overhead that reduce performance. After some changes I did some time ago, the use of original ID was not required and this only added depsgraph overhead and problems. This change solves the problems with updates in render mode. Related to T57484 and the changes requested by Sergey. |
January 30, 2019, 13:39 (GMT) |
Add utility function to set useful preferences for automation Smooth-view doesn't work well w/ automation. Having to close the splash each time is also annoying. |
January 30, 2019, 13:37 (GMT) |
Fix T61017: node_shader_utils did not handle diffuse_color correctly |
January 30, 2019, 13:25 (GMT) |
Test for texture paint |
January 30, 2019, 12:53 (GMT) |
Fix default material using zero alpha |
January 30, 2019, 12:53 (GMT) |
Merge branch 'master' into temp-wm-event-api |
January 30, 2019, 12:46 (GMT) |
Rename tests |
January 30, 2019, 12:18 (GMT) |
Add cursor motion utility function |
January 30, 2019, 11:00 (GMT) |
Fix (unreported) memleak when copying object and its material with GP settings. Like... seriously? |
January 30, 2019, 10:46 (GMT) |
Fix T60957: ASSERT when reloading double-linked file. Kind of funny to see that this has been missing presumably since the first version of library linking in Blender, and only gets noticed now. Then again, that was not really a critical issue, iirc write code ensures all libraries directly used get properly written, even if flags are incorrect. |
January 30, 2019, 10:38 (GMT) |
Cleanup: use proper bitflag operators. |
January 30, 2019, 10:03 (GMT) |
De-duplicate press/release with existing tap functionality |
January 30, 2019, 10:02 (GMT) |
Cleanup: Unused function argument |
January 30, 2019, 09:52 (GMT) |
Experimental event playback, use for testing events Useful for the undo system which cant easily be tested any other way. |
January 30, 2019, 09:51 (GMT) |
Cycles: improved rounding of sample chunks for resumable renders When using `--cycles-resumable-num-chunks N` to render a subset of the samples, having N close to the total number of samples causes rounding issues. For example, a file configured for 250 samples and 150 chunks should have 1.6666 sample per chunk. The old code rounded this to 2 samples per chunk, which would result in too many samples being rendered. When rendering a single chunk this doesn't matter much, but when larger chunk ranges are rendered with `--cycles-resumable-start-chunk` and `--cycles-resumable-end-chunk` the rounding errors start to add up. By multiplying with the number of chunks to render first, and only round to integers after that, this issue is solved. In the above example, rendering 3 chunks will correctly render 5 samples rather than 6. When the requested number of chunks is larger than the number of samples there will be duplicate samples (that is, sample N appearing both in chunk M and M+1). In this case a warning is printed to stderr. This is needed for T50977 Progressive render: use non-uniform sample chunks. Reviewed by: sergey Differential Revision: https://developer.blender.org/D4282 |
January 30, 2019, 09:44 (GMT) |
Fix T60974: Dyntopo crash on undo after object deleted Add the ability for undo steps to request memfile undo step added after them, useful for mode switching, where we need the data to exist for undo to enter the mode. |
Revision c3c8f48 by Campbell Barton January 30, 2019, 08:15 (GMT) |
Further fixing typos |
Revision 4a4034e by Campbell Barton January 30, 2019, 08:04 (GMT) |
Cleanup: unused assignment (error in last commit) |
|
|
|


Master Commits
MiikaHweb | 2003-2021