Revision 3025c34 by Hans Goudey May 27, 2021, 15:06 (GMT)  | 
Geometry Nodes: Expose texture and material inputs to modifier This allows choosing material and texture sockets for the group input node in the modifier. Note that currently grease pencil materials are displayed in the list, even though grease pencil data is not supported yet by geometry nodes. That is more complicated to fix in this case, since we use IDProperties to store the dynamic exposed inputs. Differential Revision: https://developer.blender.org/D11393  | 
Revision 24b2482 by Hans Goudey May 27, 2021, 15:00 (GMT)  | 
Cleanup: Fix forward declaring class with "struct"  | 
Revision a3edf4a by Hans Goudey May 27, 2021, 14:50 (GMT)  | 
Fix build error: Make CurveEval a struct We need a pointer to this in DNA, which means it cannot be a class.  | 
Revision e8ca635 by Ray molenkamp May 27, 2021, 14:10 (GMT)  | 
Cleanup: rename blender-launcher source file. blender-laucher.c was not an ideal name for this file since it's not directly clear it is windows only. This change renames it to blender_launcher_win32.c to be more in line with other win32 specific files we have.  | 
Revision ac83310 by Hans Goudey May 27, 2021, 14:08 (GMT)  | 
Geometry Nodes: Draw curve data in the viewport This patch adds relatively small changes to the curve draw cache implementation in order to draw the curve data in the viewport. The dependency graph iterator is also modified so that it iterates over the curve geometry component, which is presented to users as `Curve` data with a pointer to the `CurveEval` The idea with the spline data type in geometry nodes is that curve data itself is only the control points, and any evaluated data with faces is a mesh. That is mostly expected elsewhere in Blender anyway. This means it's only necessary to implement wire edge drawing of `CurveEval` data. Adding a `CurveEval` pointer to `Curve` is in line with changes I'd like to make in the future like using `CurveEval` in more places such as edit mode. An alternate solution involves converting the curve wire data to a mesh, however, that requires copying all of the data, and since avoiding it is rather simple and is in-line with future plans anyway, I think doing it this way is better. Differential Revision: https://developer.blender.org/D11351  | 
Revision 5621a8e by Hans Goudey May 27, 2021, 13:37 (GMT)  | 
Fix T88452: Point Separate crash on curve component The point separate node should create a point cloud from control points in this case, but for now disable the node on curves to avoid the crash.  | 
Revision a12fd5c by Hans Goudey May 27, 2021, 13:27 (GMT)  | 
Cleanup: Use consistent variable names  | 
Revision 5721c89 by Campbell Barton May 27, 2021, 12:44 (GMT)  | 
Cleanup: rename BKE_main_id_{clear_newpoins => newptr_and_tag_clear} It wasn't obvious this function cleared the tag as well.  | 
May 27, 2021, 12:42 (GMT)  | 
Cleanup: remove duplicate LIB_TAG_NEW untag code This patch removes unnecessary calls to `BKE_main_id_tag_all` where the same job is done by `BKE_main_id_clear_newpoins` on the following line. Reviewed By: campbellbarton, mont29 Ref D11379  | 
May 27, 2021, 12:33 (GMT)  | 
LineArt: List Optimization for tile linked data. Use array instead of ListBase for line art bounding area linked triangles and edges. Reviewed By: Sebastian Parborg (zeddb) Differential Revision: https://developer.blender.org/D11302  | 
May 27, 2021, 10:47 (GMT)  | 
Cleanup: Line art variable naming. Change `reln` to `eln`. Reviewed By: Sebastian Parborg (zeddb) Differential Revision: https://developer.blender.org/D11411  | 
Revision 42fba7f by Bastien Montagne May 27, 2021, 09:55 (GMT)  | 
LibOverride: Add heuristic protection against infinite loop due to libraries inter-dependencies. This is not supposed to happen, but better be safe than sorry, and assume it is beyond unlikely that someone would use chains of over 10k linked libraries.  | 
Revision bf7a67c by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Refactor: Rename pass accessor in viewport parameters No need to state that it is a viewport display pass, since the method is within viewport parameters it is implied that parameters do belong to the viewport. Brings this code closer to the Cycles-X branch.  | 
Revision 4ea7742 by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Refactor: Remove friend class from Cycles viewport parameters Such pattern should only be used when it is really needed. Otherwise just stick to a more regular design, without worrying who is the user of the class. Otherwise it will be annoying to subclass or unit test.  | 
Revision 8f43e31 by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Cleanup: const qualifier of return type  | 
Revision 15df83e by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Cleanup: Use logical OR in Cycles background shader  | 
Revision 616b071 by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Refactor: Naming in Cycles viewport methods Makes it more explicit they operate on shading/light. Gives room to move more viewport related settings into this class and cover with specific or generic modification checks.  | 
Revision 7b5f4c8 by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Cleanup: Redundnat member init in Cycles viewport parameters  | 
Revision 2414a57 by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Refactor: Move display pass to Cycles viewport parameters Allows to centralize storage and modification checks in a single place, avoiding duplication in the synchronization code. Ideally we would somehow be able to more granularly modify Cycles side objects. Leaving this for a future decision, because it might be better to implement it as a graph on the sync side.  | 
Revision ac2266f by Sergey Sharybin May 27, 2021, 09:36 (GMT)  | 
Cleanup: Unused include in Cycles  | 
| 
 | 
|


 Master Commits
MiikaHweb | 2003-2021