Revision 2f60e5d by Dalai Felinto January 28, 2021, 21:44 (GMT) |
Cleanup: Move geonodes object info RNA enum This enum is only used by the node. So it does not need to be declared outside the scope of its function. Originally I thought this may be relevant to the collection info node as well, but the patch for it is defining its own enums. |
Revision 7a62574 by Hans Goudey January 28, 2021, 19:52 (GMT) |
Cleanup: Reduce variable scope Also some minimal white space changes |
Revision fcb7b0a by Jacques Lucke January 28, 2021, 16:03 (GMT) |
Fix T85157: join node not working when the second mesh is empty The issue was that the `offset` in `dst_span[offset]` was out of bounds when the domain size is 0. The fix is to simply skip copying attributes in that case. |
Revision a51ff52 by Brecht Van Lommel January 28, 2021, 12:16 (GMT) |
Fix alpha transparency slider range being influenced by RGB values For buttons that edit array properties, the soft min/max and slider ranges are based on the range of all values in the array. However for alpha this does not make much sense, the only reasonable range is 0..1 even when there are RGB values larger than 1. So treat alpha as an individual property. |
Revision 1339664 by Brecht Van Lommel January 28, 2021, 12:16 (GMT) |
Revert "Depsgraph: Remove redundant copy-on-write operations" This reverts commit 76fd41e9db19dd2a33fae0e690f76792b13d49ed. This should have been reverted along with 0f95f51361d73fbd8ba8d80b3b65da930dcf3b20, since this change by itself is causing crashes when the depsgraph accesses a non-existent copy-on-write component. Ref T84717 |
Revision 3c7d5ec by Alexander Gavrilov January 28, 2021, 11:42 (GMT) |
Surface Deform: fix binding vertex artifacts causing spikes. There are two issues here. First, like in T81988 there are cases where the modifier would deform some vertices immediately after bind. This is caused by wrong assumptions in the code about the possible relative angles between various vectors, which can cause negative weights that don't blend correctly to appear. Specifically, it seems originally the code assumes that the centroid-point vector in the polygon plane lies somewhere between the mid-edge vectors. This is however not necessarily the case for distant vertices, because the polygon is not guaranteed to be truly planar, so normal projection may be a bit off. The code has to use signed angles and checks to support all possible angular arrangements. The second issue is very thin and long triangles, which tend to be very spatially unstable in their thin dimension, resulting in excess deformation. The code was weighting distance using the distances between the centroid and the mid-edge points, which in this case end up as nearly opposite vectors of sizable length and don't correctly represent how thin the triangle actually is. It is thus better to use centroid-to-line distances, and an additional even stricter value for the midpoint that will use only 3 vertices at evaluation time. Differential Revision: https://developer.blender.org/D10065 |
Revision a6b31af by Julian Eisel January 28, 2021, 11:36 (GMT) |
Merge branch 'blender-v2.92-release' |
January 28, 2021, 11:36 (GMT) |
Fix T83935: Superimposed icon's hotspot is misaligned Now the icon's rect are drawn wider than it should be, and with overlapping, probably in order to compensate for the icon's offsets inside the rect. The solution is to draw icon's rect of the correct size and center the icon itself. And make the hotspot exactly match the icon's rect. The last/right button's hotspot also covers the extra padding on the right. Differential Revision: https://developer.blender.org/D9936 Reviewed by: Julian Eisel |
January 28, 2021, 11:33 (GMT) |
Fix T83935: Superimposed icon's hotspot is misaligned Now the icon's rect are drawn wider than it should be, and with overlapping, probably in order to compensate for the icon's offsets inside the rect. The solution is to draw icon's rect of the correct size and center the icon itself. And make the hotspot exactly match the icon's rect. The last/right button's hotspot also covers the extra padding on the right. Differential Revision: https://developer.blender.org/D9936 Reviewed by: Julian Eisel |
Revision c0d2b10 by Julian Eisel January 28, 2021, 11:23 (GMT) |
Fix T69001: Custom icons won't load while using workbench engine Preview icons (e.g. material preview or other data-block previews) use the same background-job code as deferred loading of custom icons/previews. There was a check to skip preview generation if the render engine does not support preview rendering mode, which workbench doesn't. However this check should only be used when actually rendering a preview, not when doing deferred loading. |
Revision 0bd2f18 by Campbell Barton January 28, 2021, 11:11 (GMT) |
Merge branch 'blender-v2.92-release' |
Revision 07e66f5 by Campbell Barton January 28, 2021, 11:06 (GMT) |
Fix T85121: Sequencer key conflict with Lock & Select Linked "Lock Strips" (Shift-L), conflicted with "Select Pick Linked". Use Ctrl-H, Ctrl-Alt-H for lock & unlock since selected linked uses bindings which are used in other parts of Blender. |
Revision a64a8d2 by Campbell Barton January 28, 2021, 11:02 (GMT) |
Cleanup: spelling Also remove replace 'playblast' with terminology used in Blender's UI. |
Revision dfcfc8e by Campbell Barton January 28, 2021, 10:56 (GMT) |
Merge branch 'blender-v2.92-release' |
Revision 8948f73 by Campbell Barton January 28, 2021, 10:53 (GMT) |
Fix T81334: Python view-port drawing depth-test regression Since 216d78687d2b9468b05fb598d1cef0b8424a40d2 the depth function (glDepthFunc) was left in an undefined state for drawing callbacks that use the `bgl` module. This meant enabling depth-test from Python's bgl module also needed to set the depth function (which previously wasn't necessary). Set the depth function as part of GPU_bgl_start |
Revision bf721fb by Sergey Sharybin January 28, 2021, 10:34 (GMT) |
Fix panning with Lock-to-Selection and no selection in Clip Editor Rather self-explanatory. Never worked since the initial implementation. It is possible to preserve lock-to-selection option with no selection nowadays (since the fix for T84850). So now the Lock-to-Selection option is fully under user control. Surely, the panning and zooming is also properly supported now in the described scenario. Differential Revision: https://developer.blender.org/D10226 |
Revision 3b66f40 by Bastien Montagne January 28, 2021, 10:33 (GMT) |
Fix T85124: Undo assert changing property in redo panel. Logical mistake in recent refactor (rB2a8122fb65c5). |
Revision 573bda1 by Sergey Sharybin January 28, 2021, 10:05 (GMT) |
Fix unused result from mmap() call The unused result was reported by Clang-Tidy 11. It does make sense to check for the failed mmap() calls rather than quietly suppress errors. In this change failures are reported, but application execution is not aborted. This is a bit disputable, but it feels to be a safer thing to do now. It is unclear how to test the code though, as we don't have any tools in-place to simulate read errors. Differential Revision: https://developer.blender.org/D10223 |
Revision 92567c0 by Antonio Vazquez January 28, 2021, 10:02 (GMT) |
Cleanup: Fix clang format Due a problem in the mergetool, the clang format was totally wrong in the previous commit. |
Revision 8214a63 by Sergey Sharybin January 28, 2021, 09:54 (GMT) |
Merge branch 'blender-v2.92-release' |
|
|
|


Master Commits
MiikaHweb | 2003-2021