May 6, 2021, 09:25 (GMT) |
Cleanup: clang-tidy |
May 6, 2021, 09:25 (GMT) |
Minor updates to i18n spellcheck tool. |
May 6, 2021, 09:25 (GMT) |
LibOverride: temporarily fix the material driver workaround with a hack. Currently overriding properties within material node trees is not supported. However there is a workaround that allows feeding values through drivers via an intermediate custom property, as described in T82404. The workaround relies on the behavior of the ID copying code that always patches datablock self-references even without any overrides. Unfortunately, this broke during development of 2.93. This happened because a call RNA_struct_override_matches added in rB2281db72b0157 detects that no override exists, and 'restores' the self-reference to point to the original datablock. To avoid this, mark the Material.node_tree property with the PROPOVERRIDE_IGNORE flag to stop RNA_struct_override_matches from recursing into the currently unsupported node tree sub-block. This flag should be removed when this is properly supported. This was confirmed to fix the workaround and discussed with @mont29. |
May 6, 2021, 09:25 (GMT) |
Geometry Nodes: Parallelize attribute nodes This commit significantly speeds up many of the attribute nodes when multiple threads are available in linear situations when parallelism cannot be achieved elsewhere. See the differential for a table of timing comparisons tested on a Ryzen 3700x. For an attribute with 4 million elements, the nodes were about 3 to 9 times faster. The changes are not exhaustive, other nodes could still be parallelized in the future. Also, it would be possible to further optimize the grain size in `parallel_for`, but I'd rather make sure it isn't too small. I tested some different values, but also relied on intuition-- increasing grain size for less complex operations and vice versa. Differential Revision: https://developer.blender.org/D11139 |
May 6, 2021, 09:25 (GMT) |
Fix T87989: Crash using OpenCL in compositor Initial report was mentioning the Classroom demo scene, but this is probably because the scene was pre-configured to be used with OpenCL. Would expect any OpenCL compositing to be failing prior to this fix. The reason why crash was happening is due to OpenCL queue being released from OpenCLDevice destructor. Is not that obvious, but when Vector (including std::vector) is holding elements by value a destructor will be called on "old" memory when vector capacitance changes. Solved by making forbidding copy semantic for compositor devices and forcing move semantic to be used. Also use emplace semantic in the devices vector initialization. |
May 6, 2021, 09:25 (GMT) |
Fix compilation error after recent compositor fix Apparently, there is no emplace semantic available in the Vector in the stable branch. |
May 6, 2021, 09:25 (GMT) |
Fix T87969: crash accesing FaceMaps / PaintMask data in editmode Workaround for crash when accessing FaceMaps / PaintMask data in editmode, just disallow access in editmode as is done with UVs. Same fix as in {rB3e2619b3e72a}. Maniphest Tasks: T87969 Differential Revision: https://developer.blender.org/D11146 |
May 6, 2021, 09:25 (GMT) |
Cleanup: use boolean for has_event variable & return value |
May 6, 2021, 09:25 (GMT) |
Alembic Procedural: refactor data reading This splits the data reading logic from the AlembicObject class and moves it to separate files to better enforce a separation of concern. The goal was to simplify and improve the logic to read data from an Alembic archive. Since the procedural loads data for the entire animation, this requires looping over the frame range and looking up data for each frame. Previously those loops would be duplicated over the entire code causing divergences in how we might skip or deduplicate data across frames (if only some data change over time and not other on the same object, e.g. vertices and triangles might not have the same animation times), and therefore, bugs. Now, we only use a single function with callback to loop over the geometry data for each requested frame, and another one to loop over attributes. Given how attributes are accessed it is a bit tricky to simplify further and only use a ingle function, however, this is left as a further improvement as it is not impossible. To read the data, we now use a set of structures to hold which data to read. Those structures might seem redundant with the Alembic schemas as they are somewhat a copy of the schemas' structures, however they will allow us in the long run to treat the data of one object type as the data of another object type (e.g. to ignore subdivision, or only loading the vertices as point clouds). For attributes, this new system allows us to read arbitrary attributes, although with some limitations still: * only subdivision and polygon meshes are supported due to lack of examples for curve data; * some data types might be missing: we support float, float2, float3, booleans, normals, uvs, rgb, and rbga at the moment, other types can be trivially added * some attribute scopes (or domains) are not handled, again, due to lack of example files * color types are always interpreted as vertex colors |
May 6, 2021, 09:01 (GMT) |
Merge branch 'blender-v2.93-release' |
May 6, 2021, 09:00 (GMT) |
Fix T87983: Motion tracker button tooltips identical The tooltips for the tracker buttons were all equal (because they all use the same operator). This adds the `get_description` operator callback to the `CLIP_OT_track_markers` operator and returns a more descriptive tooltip for the different buttons. Reviewed By: mont29 Maniphest Tasks: T87983 Differential Revision: https://developer.blender.org/D11145 |
May 6, 2021, 08:43 (GMT) |
Merge branch 'master' into temp-gpencil-bezier-stroke-type |
May 6, 2021, 08:42 (GMT) |
GPencil: Bezier stroke smooth modifer This commits adds an extension of the `BKE_gpencil_editcurve_smooth` function. `BKE_gpencil_editcurve_smooth_ex` allows the use of vertex groups and curve mappings. This new function is used to implement the smooth modifier for bezier strokes. |
May 6, 2021, 07:26 (GMT) |
GPencil: Initial bezier support for smooth modifier This adds the `deformBezier` callback for the smooth modifier. At the moment this does not support vertex group influence and custom curve falloff. |
May 6, 2021, 06:44 (GMT) |
Merge branch 'blender-v2.93-release' |
May 6, 2021, 06:30 (GMT) |
Fix T86314: materials not updated correctly after collada import (again) While rB6b18678e34bf did the correct updates, it did it a bit early (not covering all possible node tree changes). Now do the ntreeUpdateTree() at the very end of the material import instead. Thx @scurest investigating. Maniphest Tasks: T86314 Differential Revision: https://developer.blender.org/D11159 |
May 6, 2021, 06:29 (GMT) |
Fix radius not taken into account when adding curve guide force field Wrong usage of ED_curve_add_nurbs_primitive from {rBe8f3fa99de81}. Differential Revision: https://developer.blender.org/D11166 |
May 6, 2021, 05:34 (GMT) |
Merge branch 'blender-v2.93-release' |
May 6, 2021, 05:09 (GMT) |
Fix memory leak in object.mode_set_with_submode |
May 6, 2021, 03:57 (GMT) |
Cleanup: VSE: move functions from incorrect file `SEQ_recursive_apply` and `SEQ_seqbase_recursive_apply` were incorrectly refactored into `iterator.c` file, but they aren't part and don't use sequencer iterator. Functions are moved to `utils.c` file. |
|
|
|


Master Commits
MiikaHweb | 2003-2021