Revision 0f78a57 by Sergey Sharybin June 19, 2020, 10:02 (GMT) |
Make BLI_edgehash_test compatible with C++17 random_shuffle was removed (at least the used version). |
Revision 31ae833 by Sergey Sharybin June 19, 2020, 10:02 (GMT) |
Ceres: Update to the latest upstream version Using latest master because of various compilation error fixes. Brings a lot of recent development. From most interesting parts: - New threading model. - Tiny solver. - Compatibility with C++17. |
Revision 171c4fb by Sergey Sharybin June 19, 2020, 10:02 (GMT) |
Update C++ standard to C++14 This is an intermittent state to get all dependencies to compile. For example, the latest Ceres is needed to bring C++17 support, but it has bumped minimal requirement to C++14. |
Revision 9e70129 by Alexander Gavrilov June 19, 2020, 09:17 (GMT) |
Cloth: allow forces to act parallel to cloth. Currently all force effectors can only act on cloth when the force is perpendicular to the surface. This makes sense for wind, but not for other forces; and the user may want even wind to have some friction. This changes effector code to output two force vectors - although you of course can pass the same pointer for both. The force is split between the two outputs based on a new per-effector setting. Differential Revision: https://developer.blender.org/D8017 |
Revision f382109 by Antonio Vazquez June 19, 2020, 08:56 (GMT) |
Fix T78024: GPencil - Add missing UV Fill prop to RNA This was changed in the refactor done in 2.83 and was not included by error. |
Revision 2dff08c by Sybren A. Stüvel June 19, 2020, 08:24 (GMT) |
Alembic: always export transforms as inheriting Blender now always exports transforms as as "inheriting", as Blender has no concept of parenting without inheriting the transform. Previously only objects with an actual parent were marked as "inheriting", and parentless objects as "non-inheriting". However, certain packages (for example USD's Alembic plugin) are incompatible with non-inheriting transforms and will completely ignore such transforms, placing all such objects at the world origin. When importing non-inheriting transforms from Alembic, Blender will break the parent-child relation and thus force the child to (correctly) interpret the transform as world matrix. |
Revision f106369 by Sybren A. Stüvel June 19, 2020, 08:24 (GMT) |
Alembic: prevent spaces in names of exported particle systems Other types already had spaces, periods, and colons replaced by underscores. The upcoming Alembic exporter (based on the `AbstractHierarcyIterator` class) will be more consistent and apply the same naming rules everywhere. This is in preparation for that change. The `get_?_name()` functions in `abc_util.{cc,h}` will be removed then. |
Revision 0d744cf by Sybren A. Stüvel June 19, 2020, 08:17 (GMT) |
Alembic: export object data with object data name Previously the Alembic exporter exported a mesh object to `{object.name}/{object.name}Shape`. Now it exports to `{object.name}/{mesh.name}` instead. The same change also applies to other object data types. Note that the code now is a bit hackish, as `m_name` is set even in cases where it isn't used. This hackishness was already there, though, but it's now just more visible. This will all be cleaned up when the Alembic exporter is ported to use the `AbstractHierarchyImporter` structure of the Universal Scene Description (USD) exporter. Reviewed By: mont29 Differential Revision: https://developer.blender.org/D7672 |
Revision 0ae7883 by Sybren A. Stüvel June 19, 2020, 08:17 (GMT) |
IO: ensure export path and export name are always consistent Before this, there was one code path that set `context.export_path`, and a different code path for `context.export_name`, allowing the two to diverge. Keeping track of the export path of the export parent (which can be, but is not always, the Blender parent object) also allows a concrete subclass of `AbstractHierarchyIterator` to find the `AbstractWriter` for the export parent. In case of exporting to Alembic this is important, as it's not possible to simply give the Alembic library the full export path of an object like we do in the Universal Scene Description (USD) exporter; Alembic needs the C++ object of the parent. |
Revision 69c3d98 by Sybren A. Stüvel June 19, 2020, 08:17 (GMT) |
IO: Allow exporting a subset of the writers This is in order to prepare for compatibility with the Alembic exporter. That exporter is capable of writing object transforms and object data at different (sub)frames. The rename from `created_writers` to `used_writers` is necessary, as not all created writers will be actually used in each iteration. The Universal Scene Description (USD) exporter does not make use of this. Reviewed By: mont29 Differential Revision: https://developer.blender.org/D7670 |
Revision 084c5d6 by Sybren A. Stüvel June 19, 2020, 08:17 (GMT) |
IO: Move Abstract Hierarchy Iterator into `io/common` The goal of the `AbstractHierarchyIterator` class (and supporting classes) was to use it in different exporters. It shouldn't be part of the USD module + namespace any more, now that it will also be used in the upcoming Alembic exporter rewrite. The source files are moved into `io/common`, which is compiled & linked into a new library `bf_io_common`. The unittests are still inside the `tests/gtests/usd` directory. They should be moved to a separate test module too, but that will be delayed until after T73268 has been resolved. Reviewed By: mont29 Differential Revision: https://developer.blender.org/D7669 |
Revision b1ce4ca by Antonio Vazquez June 19, 2020, 08:10 (GMT) |
Fix T77997: GPencil insert keyframe on timeline doen't update viewport The reason was the datablock is changed but it was not tagged for depsgraph refresh. In some cases it could be possible to tag several times the same datablock, but as this is not the case all the times and the number of tags is always very small, it doesn't worth a complex code to keep a memory list of the datablocks to tag. |
Revision fade37f by Campbell Barton June 19, 2020, 06:47 (GMT) |
Writefile: move file flags to BlendFileWriteParams This removes G_FILE_HISTORY, G_FILE_SAVE_COPY & G_FILE_USERPREFS. Using file-flags made logic harder to follow since it's not so clear which flags are expected to be in G.fileflags & which are meant to be set and passed as arguments, these are shared between read & write functions too. Add BlendFileWriteParams so options which don't need to be stored aren't mixed up with flags that are stored for reuse. |
Revision 5a77f64 by Jeroen Bakker June 19, 2020, 06:13 (GMT) |
Cleanup: SPACE_ACTION does not have a RGB_TYPE_TOOL_HEADER So no need to check this specific case. |
Revision d093f61 by Jeroen Bakker June 19, 2020, 06:11 (GMT) |
Cleanup: use bool and enums in `match_region_with_redraws` Function used int for everything. |
Revision 642b19c by Campbell Barton June 19, 2020, 04:29 (GMT) |
Revision 41f0697 by Nathan Craddock June 19, 2020, 03:53 (GMT) |
Outliner: Show pose group icons Pose groups previously showed a dot icon. Now it draws the correct icon. |
Revision 1ee32ea by Campbell Barton June 19, 2020, 03:17 (GMT) |
Cleanup: use doxy sections |
Revision 0479c28 by Pablo Vazquez June 19, 2020, 00:04 (GMT) |
Cleanup commented separator. |
Revision f1e5fd0 by Campbell Barton June 18, 2020, 23:44 (GMT) |
Cleanup: unsupported ATTR_FALLTHROUGH use, clang-format |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021