May 8, 2020, 16:05 (GMT) |
install_deps: Fix (unreported) typo in OpenXR build code. Was breaking up proper behavior of 'need to rebuild' checks for that lib. |
May 8, 2020, 16:05 (GMT) |
install_deps: Fix (unreported) broken logic in OIIO building. Not sure where that code was comming from, but it was breaking the cleanup/update_deps logic... |
May 8, 2020, 16:05 (GMT) |
install_deps: Fix (unreported) broken Boost source URL. |
May 8, 2020, 16:05 (GMT) |
Cleanup: install_deps: Simplify the 'no distro' code a bit. We never deal with packages then, and only ever build (if we do anything), no reason to make things more complicated than needed... |
May 8, 2020, 16:05 (GMT) |
install_deps: Fix (unreported) bad handling of deps between libs. Previous code would forec built libs to always be rebuilt when one of their deps was using a package. While this could be useful when said package was actually updated, this generates way too much false positives. Now only rebuild a built lib when we actually switch from built to package for one of its deps. |
May 8, 2020, 16:01 (GMT) |
Windows: Include symbol file in module information When writing out the module information in a crashdump we did not include what symbol file was loaded and if that symbol file actually matches our executable. Given the backtraces may contain invalid information if the symbols are unmatched this is relevant to know. This diff adds the symbol file and an indication if unmatched symbols are used. |
May 8, 2020, 15:46 (GMT) |
Windows: Improve private symbol detection To detect if private of public symbols were loaded we were relying on a strcmp with a known filename, which was not great, the symbol api has a field we can query which should be more flexible and reliable. |
May 8, 2020, 15:43 (GMT) |
Alembic: export object data with object data name The old exporter always 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 USD. Differential Revision: https://developer.blender.org/D7672 |
May 8, 2020, 15:39 (GMT) |
Windows: Fix BLI_assert backtrace. With the recent backtrace overhaul, the fact that BLI_assert calls BLI_system_backtrace slipped somehow trough the cracks, causing issues for debug builds. This change allows BLI_system_backtrace to run again without having an exception record. Also minor improvements to the comments. |
May 8, 2020, 15:35 (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 (it needs the C++ object of the parent). |
May 8, 2020, 15:32 (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. Differential Revision: https://developer.blender.org/D7670 |
May 8, 2020, 15:28 (GMT) |
Remove unnecessary include directories from CMakeLists.txt |
May 8, 2020, 15:28 (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. 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. Differential Revision: https://developer.blender.org/D7669 |
May 8, 2020, 15:28 (GMT) |
USD: Export hair/particle system with name of system (and not its settings) Particle systems have two names: the name of the particle system itself, and the name of the particle system settings. The USD exporter used to use the latter name, and now switched to the former. This is to be in line with the Alembic exporter, as well as to give users more freedom in the naming (the particle system can have a unique name but still share settings from other particle systems). |
May 8, 2020, 15:09 (GMT) |
Merge branch 'master' into panel-list-patch |
May 8, 2020, 15:06 (GMT) |
Review feedback |
May 8, 2020, 15:03 (GMT) |
Merge branch 'blender-v2.83-release' |
May 8, 2020, 14:59 (GMT) |
Fluid: Adjusted secondary particles timestep and gravity options Secondary particles are now compatible with the new gravity setup. |
May 8, 2020, 14:59 (GMT) |
Fluid: Updated Mantaflow source files Includes more flexible options for dt, dx in secondary particles plugin. |
May 8, 2020, 14:49 (GMT) |
Fix T65012: Update depsgraph for matcap flipping The matcap flipping didn't work with the workbench engine in rendered mode because of a missing depedency graph update. This commit tags the scene id for a dependency graph update in `toggle_matcap_flip`. Reviewed By: fclem, sergey Differential Revision: https://developer.blender.org/D7657 |
|
|
|


Master Commits
MiikaHweb | 2003-2021