December 14, 2020, 13:57 (GMT) |
Fix memory leak and possible other issues with custom previews Mistake in 812ea9184221. Fixed that same one before in the branch, I may have brought it back when resolving merge conflicts. |
December 14, 2020, 13:54 (GMT) |
Another attempt at fixing numpy path issue. |
December 14, 2020, 13:35 (GMT) |
Some more debug prints i build system... |
December 14, 2020, 12:52 (GMT) |
Merge branch 'master' into cycles_procedural_api |
December 14, 2020, 12:44 (GMT) |
Fix T75539: Cycles missing geometry update when switching displacement method The shaders were not tagged for a needed geometry update when the displacement method was modified, neither were the Geometry and Object managers. Reviewed By: kevindietrich Maniphest Tasks: T75539 Differential Revision: https://developer.blender.org/D8896 |
December 14, 2020, 12:41 (GMT) |
apply changes from alembic review branch |
December 14, 2020, 12:33 (GMT) |
Merge branch 'master' into cycles_procedural_api |
December 14, 2020, 12:17 (GMT) |
UI/Assets: Support generating object preview images Object previews are really helpful for visual data-block selection, like asset browsing. Having them be generative should also be quite handy and should work well enough in many, if not most cases. What this does is simple: * Place the object (actually a deep copy of it, for thread safety) in a virtual .blend into an empty scene/view-layer. * Add a camera, point it towards the front of the object, assuming that means pointing towards its +Y axis. * Use "Camera Fit Frame to Selected" logic to put the object into frame. * Create a threaded off-screen render. Of course, such an automatic preview will not work in all situations. E.g. it currently does a bad job capturing a single plane. We could add options for more advanced automatic previews, but probably custom previews is more important, which I committed already (812ea9184221). Part of the first Asset Browser milestone. Check the #asset_browser_milestone_1 project milestone on developer.blender.org. Reviewed as part of https://developer.blender.org/D9719. Reviewed by: Bastien Montagne, Brecht Van Lommel |
December 14, 2020, 12:08 (GMT) |
Blenkernel: move DerivedMesh.c to c++ Required changes to make it compile with clang tidy: * Use c++ includes like (e.g. climits instead limits.h). * Insert type casts when casting from void* to something else. * Replace NULL with nullptr. * Insert casts from int to enum. * Replace designed initializers (not supported in C++ yet). * Use blender::Vector instead of BLI_array_staticdeclare (does not compile with C++). * Replace typedef statements. Ref T83357. |
December 14, 2020, 12:01 (GMT) |
CMake: More verbose message in `find_python_package` |
December 14, 2020, 11:33 (GMT) |
Fix several issues with handling of numpy in CMake. Issues were: * Abusing of `WITH_PYTHON_INSTALL_NUMPY` by both Audaspace and Mantaflow. - `PYTHON_INSTALL` options only decide whether we copy python (and some extra modules) in our Blender installation. On linux it makes much more sense to use global python installation. - Now we have instead a proper `WITH_PYTHON_NUMPY` * Bad assumptions regarding path of headers relative to path of python module. - In current Debian testing, modules are under `python3.9` directory, while headers are under `python3` directory. - Now we properly `find_path` for headers as well, modifying `find_python_package` to take an optional argument for headers. Note that the required changes done to `extern` libraries are in blender-specific files that do not exist upstream. Differential Revision: https://developer.blender.org/D9773 |
December 14, 2020, 11:31 (GMT) |
Merge branch 'master' into experimental-build |
December 14, 2020, 11:29 (GMT) |
Revert "Fix several issues with handling of numpy in CMake." This reverts commit 5d570c875eda8fb9aa3635f7f4edac0dc1eaedc8. Buildbots are still borken, need more time to investigate. |
December 14, 2020, 11:29 (GMT) |
Revert "Fix own error in rB5d570c875eda in CMake script." This reverts commit 6da609fcb365f2e51299045b7d5e93fd17583f54. Buildbots are still broken, need more time to investigate. |
December 14, 2020, 11:23 (GMT) |
Fix own error in rB5d570c875eda in CMake script. My mistake, though CMake could handle default arguments but it needs to be explicitly passed actually. |
December 14, 2020, 11:16 (GMT) |
UI/Assets: Operator to load custom preview images for data-blocks No automatic preview generation will ever be good enough to cover all cases well. So custom preview images are a must for a preview driven data-block selection - like for asset browsing. The operator simply allows selecting an image file, which will then be read and copied into the data-blocks preview (resized if necessary). There's no UI for this currently and the operator won't be available in the search menu yet. It will later once the Asset Browser UI is merged. Reviewed as part of https://developer.blender.org/D9719. Reviewed by: Bastien Montagne, Brecht Van Lommel |
December 14, 2020, 11:09 (GMT) |
Fix windows build. |
December 14, 2020, 10:37 (GMT) |
LibOverride: Do not store some heavy data from override IDs. This commit removes geometry from meshes and shapekeys, and embedded files, from liboverride IDs. This data is never overrideable, there is no reason to store extra useless copies of it in production files. See T78944. Note that we may add more data to be skipped on write for liboverrides in the future, but this commit should address all the most important cases already. Reviewed By: brecht Differential Revision: https://developer.blender.org/D9810 |
December 14, 2020, 10:31 (GMT) |
GPencil: Add missing Pin icon for default eraser This icon allows to set the default eraser when press Ctrl key and was removed by error in the brush refactor. |
December 14, 2020, 10:00 (GMT) |
Fix several issues with handling of numpy in CMake. Issues were: * Abusing of `WITH_PYTHON_INSTALL_NUMPY` by both Audaspace and Mantaflow. - `PYTHON_INSTALL` options only decide whether we copy python (and some extra modules) in our Blender installation. On linux it makes much more sense to use global python installation. - Now we have instead a proper `WITH_PYTHON_NUMPY` * Bad assumptions regarding path of headers relative to path of python module. - In current Debian testing, modules are under `python3.9` directory, while headers are under `python3` directory. - Now we properly `find_path` for headers as well, modifying `find_python_package` to take an optional argument for headers. Note that the required changes done to `extern` libraries are in blender-specific files that do not exist upstream. Differential Revision: https://developer.blender.org/D9773 |
|
|
|


Master Commits
MiikaHweb | 2003-2021