Revision 8034b27 by Jacques Lucke March 29, 2021, 08:54 (GMT) |
Fix T86876: cannot modify float properties of geometry nodes modifier from Python Previously, the code expected the id property to have the `IDP_FLOAT` type. However, when assigning a Python float (which is a double internally) to an id property, it would change the type to `IDP_DOUBLE`. The fix is to allow both types in the geometry nodes modifier. |
Revision fa1569a by Jacques Lucke March 29, 2021, 08:14 (GMT) |
Fix T86966: crash when rendering with geometry nodes UI hints should only be modified when the depsgraph is active. Otherwise two threads evaluating the same object in different depsgraphs can conflict with each other. |
Revision 4e34bad by Jeroen Bakker March 29, 2021, 07:57 (GMT) |
Overrides: Make Experimental API Fail On Usage. It used to give a warning so test cases couldn't fail. This has been changed in the test case so we could use an error here. |
Revision 87f9405 by Jeroen Bakker March 29, 2021, 07:54 (GMT) |
Overrides: API to create an override template. This is functionality that isn't accessible via the user interface. The API allows the creation and modification of an override template that holds rules that needs to be checked when overriding the asset. The API is setup that it cannot be changed after creation. Later on when the system is more mature we will allow changing overrides operations. NOTE: This is an experimental feature and should not be used in productions. Reviewed By: mont29, sebbas Differential Revision: https://developer.blender.org/D10792 |
Revision 27fa250 by Jacques Lucke March 29, 2021, 07:35 (GMT) |
Fix T86972: transform node transforms shape keys |
Revision 240f15c by Campbell Barton March 29, 2021, 07:30 (GMT) |
Comments: improve docstring for ED_view3d_clipping_test The meaning of the return value wasn't obvious. |
Revision b9734f7 by Jeroen Bakker March 29, 2021, 07:25 (GMT) |
Cleanup: Remove unused node.c. Was wrongly added back with the anti aliasing node patch. |
Revision fc88961 by Campbell Barton March 29, 2021, 07:08 (GMT) |
Fix vert/edge knife snapping when the cursor wasn't over a face In this case, the cage location was left zeroed which was then projected back onto the screen to find the nearest screen space edge/vertex. This made snapping to the vertex/edge fail in some corner-cases where it was intended to work. |
Revision 8994f09 by Campbell Barton March 29, 2021, 07:08 (GMT) |
Knife: scale points & snapping threshold by the DPI factor The points were too small on hi-dpi displays. |
Revision 3659340 by Campbell Barton March 29, 2021, 07:08 (GMT) |
Cleanup: logical error in path select picking Resolve logical error in edbm_shortest_path_pick_invoke where any discrepancy between EDBM_unified_findnearest and edbm_elem_find_nearest caused the active-object to be cleared. While it's not a problem at the moment, using a larger threshold for path picking exposes the error. |
Revision 80cbbd2 by Campbell Barton March 29, 2021, 07:08 (GMT) |
Knife: support vert/edge snapping when not directly over a face Respect the distance argument to EDBM_face_find_nearest, when zero, sample a single pixel, otherwise sample a region. Knife uses the selection-buffer to pick a face when the ray-cast failed. This was meant to allow snapping to nearby faces however as the margin was ignored, it was only used in edge cases where the ray-cast missed but the pixel didn't. Now the face-picking threshold is working as expected. Note that other callers to EDBM_face_find_nearest have been updated so set their distance argument to zero so this only impacts the knife. Regular selection and path select could be modified separately if users prefer this behavior. |
Revision ab26be8 by Jeroen Bakker March 29, 2021, 06:20 (GMT) |
Cleanup: use pragma once. |
Revision 25c02ea by Jeroen Bakker March 29, 2021, 06:18 (GMT) |
Cleanup: Add namespace to compositor. |
Revision 9975af5 by Jeroen Bakker March 29, 2021, 06:04 (GMT) |
Cleanup: Add `override` Keyword. |
March 29, 2021, 05:56 (GMT) |
Compositor: Add Anti-Aliasing node This is an implementation of Enhanced Subpixel Morphological Antialiasing (SMAA) The algorithm was proposed by: Jorge Jimenez, Jose I. Echevarria, Tiago Sousa, Diego Gutierrez This node provides only SMAA 1x mode, so the operation will be done with no spatial multisampling nor temporal supersampling. See Patch for comparisons. The existing AA operation seems to be used only for binary images by some other nodes. Using SMAA for binary images needs no important parameter such as "threshold", so we perhaps can switch the operation to SMAA, though that changes existing behavior. Notes: 1. The program code assumes the screen coordinates are DirectX style that the vertical direction is upside-down, so "top" and "bottom" actually represent bottom and top, respectively. Thanks for Habib Gahbiche (zazizizou) to polish and finalize this patch. Reviewed By: jbakker Differential Revision: https://developer.blender.org/D2411 |
Revision 6af4163 by Campbell Barton March 29, 2021, 03:31 (GMT) |
Knife: reduce redundant face picking queries Reduce the maximum number of queries to find the face under the mouse cursor from 6x to 2x on cursor motion. Calculating the screen-space detail could perform 2x look-ups which have already been calculated. |
Revision 27a7b2e by Campbell Barton March 29, 2021, 02:29 (GMT) |
Fix T83391: Knife sometimes snaps to object center Knife snapping logic assumed having a face under the cursor meant the projected positions were set. This is not always the case as failure to ray-cast uses the back-buffer as a fallback. |
Revision 9289c35 by Jacques Lucke March 28, 2021, 10:50 (GMT) |
Cleanup: use parentheses in macro |
Revision e47f5cf by Jacques Lucke March 28, 2021, 10:50 (GMT) |
Cleanup: deduplicate attribute creating code |
Revision afcfc6e by Campbell Barton March 28, 2021, 08:45 (GMT) |
|
|
|


Master Commits
MiikaHweb | 2003-2021