Revision 2f0d919 by Campbell Barton January 16, 2021, 00:32 (GMT) |
Add Object Tool: quiet warning setting size The size property was only used for the cube |
Revision c4bbe44 by Campbell Barton January 16, 2021, 00:32 (GMT) |
Add Object Tool: workaround non-orthogonal orientation matrices |
Revision 8fd3ffc by Campbell Barton January 16, 2021, 00:31 (GMT) |
Add Object Tool: rename keymap, expose in keymap editor Make the name follow the convention of other View3D keymaps. |
Revision 27c142a by Campbell Barton January 16, 2021, 00:28 (GMT) |
Add Object Tool: remove from experimental Based on feedback from @dbystedt, include this in 2.92 with some updates (coming next). |
Revision a843633 by Nicholas Rishel January 15, 2021, 20:23 (GMT) |
Merge branch 'blender-v2.92-release' |
Revision 957de39 by Nicholas Rishel January 15, 2021, 20:18 (GMT) |
Fix T84645 cursor moves when clicking selector. The absolute position desktop mapping has been corrected. The correct mapping is 0-65535 inclusive. Additionally, division by the virtual desktop width and height needed to be subtracted by 1 as width and height are one more than the final pixel index. |
Revision f71a7d3 by Aaron Carlisle January 15, 2021, 19:58 (GMT) |
Cleanup: Remove Unused tracking properties These properties are unused and serve no purpose. Reviewed By: sergey, #motion_tracking Differential Revision: https://developer.blender.org/D9803 |
Revision fa817b8 by Ray molenkamp January 15, 2021, 19:36 (GMT) |
Merge remote-tracking branch 'origin/blender-v2.92-release' |
Revision de60dc8 by Ray molenkamp January 15, 2021, 19:36 (GMT) |
Fix: Build error with MSVC 2017 BKE_cryptomatte_extract_layer_name was using std::isdigit without including <cctype> somehow only MSVC 2017 had a problem with that. |
Revision bf7fdd0 by Bastien Montagne January 15, 2021, 18:36 (GMT) |
Cleanup: LibOverride: Update comment. |
Revision 2aa7bc0 by Bastien Montagne January 15, 2021, 18:27 (GMT) |
LibOverride: Also consider regular embedded IDs as virtual overrides. Those (aka root node trees and master collections) share same 'traits' as the shapekeys: RNA cannot assign them, so we need to handle them as sub-data of their owner IDs. Not sure how much this will help in improving support of overrides for scenes and nodetrees, but this is a mandatory step towards that goal for sure. |
Revision ce317c9 by Bastien Montagne January 15, 2021, 18:18 (GMT) |
LibOverride: fix/update/re-enable ID-related debug checks in diffing code. We should now have the tools to ensure consistency of ID pointers diffing in `rna_property_override_diff_propptr`. As a reminder, for most ID pointers we just check the actual pointer value, but this is not possible for embedded IDs like root node trees or master collections, and for fake embedded ones like shapekeys, so those should be handled as mere sub-data of their owner IDs in override context. |
Revision f1a577b by Bastien Montagne January 15, 2021, 18:00 (GMT) |
Merge branch 'blender-v2.92-release' |
Revision 5cf04fe by Bastien Montagne January 15, 2021, 18:00 (GMT) |
Fix (unreported) copying liboverride of mesh breaks overrides of shape keys. Our beloved shapekeys are 'virtual' overrides, they need special snowflake treatment here as well. They do not have any override data, from override perspective they are considered as mere sub-data from their owning ID (mesh, lattice, etc.). Therefore, we should not copy override data from them, but instead properly flag those new IDs as `LIB_EMBEDDED_DATA_LIB_OVERRIDE`. Found while investigating T84373. |
Revision dc69ef6 by Bastien Montagne January 15, 2021, 18:00 (GMT) |
Fix T84373: Overrides : shapes keys driven by armature don't work on second instance. Code generating override operations would not deal properly with Pointer RNA properties, trying by default to use and check pointers' names properties like it does with items of a collection. However, using name property in pointer RNA property case makes no sense, so specialize the `no_prop_name` flag for each case (pointer or collection). here, since second override would generate local data-blocks with different names than the linked data ones, name matching would fail and breck handling of override diffing in shapekeys. Note that shape keys are the only one concerned by that problem, since other embedded IDs (root node trees and master collections) are fully real ones, so they always get the same names. |
Revision 3190566 by Bastien Montagne January 15, 2021, 17:51 (GMT) |
Fix T84373: Overrides : shapes keys driven by armature don't work on second instance. Code generating override operations would not deal properly with Pointer RNA properties, trying by default to use and check pointers' names properties like it does with items of a collection. However, using name property in pointer RNA property case makes no sense, so specialize the `no_prop_name` flag for each case (pointer or collection). here, since second override would generate local data-blocks with different names than the linked data ones, name matching would fail and breck handling of override diffing in shapekeys. Note that shape keys are the only one concerned by that problem, since other embedded IDs (root node trees and master collections) are fully real ones, so they always get the same names. |
Revision 69a7015 by Bastien Montagne January 15, 2021, 17:50 (GMT) |
Fix (unreported) copying liboverride of mesh breaks overrides of shape keys. Our beloved shapekeys are 'virtual' overrides, they need special snowflake treatment here as well. They do not have any override data, from override perspective they are considered as mere sub-data from their owning ID (mesh, lattice, etc.). Therefore, we should not copy override data from them, but instead properly flag those new IDs as `LIB_EMBEDDED_DATA_LIB_OVERRIDE`. Found while investigating T84373. |
Revision 3459f75 by Hans Goudey January 15, 2021, 17:04 (GMT) |
Merge branch 'blender-v2.92-release' |
Revision 0b0e452 by Hans Goudey January 15, 2021, 17:04 (GMT) |
Geometry Nodes: Use a default value in the point scale node This commit adds the ability to provide a default value to `attribute_try_get_for_output` and uses it for the `Point Scale` node, which is important because the node uses multiplication. The idea is to keep "name-specific" functionality in nodes rather than in the attribute API, otherwise the complexity will be hard to keep track of. So this fix doesn't apply to the Attribute Vector Math node, but hopfully that is okay since that's now a lower level node for this purpose anyway. Differential Revision: https://developer.blender.org/D10115 |
Revision 237e27e by Hans Goudey January 15, 2021, 16:48 (GMT) |
Cleanup: Add const in various places in node code Also includes some various other minor cleanups, like using bool instead of int in a couple places. |
|
|
|


Master Commits
MiikaHweb | 2003-2021