Revision 70e064f by Hans Goudey 21 minutes ago |
Cleanup: Correct comments in ID type enum |
Revision c4f3475 by Campbell Barton 26 minutes ago |
Cleanup: update comment from 77f73a92843965906189dd56dcc4d18eae2371cc |
31 minutes ago |
Fix T85054: undo/redo app handlers broken Regression in recent commit c13383da416c9c99d03058caaf66c736af0272cb which swapped undo/redo when calling the handlers. Ref D10200 |
Revision eaa7265 by Julian Eisel 37 minutes ago |
Merge branch 'blender-v2.92-release' |
Revision 77f73a9 by Julian Eisel 39 minutes ago |
Fix library name clipping most of the data-block name in data-block menus Issue is visible here https://developer.blender.org/F8626313. If there is enough space for both the item name and the library hint, display both. Otherwise, clip either the item name, the library hint, or both so that not more than 60% and 40% of the available width are used repectively. There are further improvements we could do, as noted in T84188, this just fixes the regression for the release. Part of T84188. There were multiple reports about this, see merged in and mentioned reports in T84188 and T78012. |
Revision a35c0fe by Campbell Barton 1 hour 33 min ago |
Merge branch 'blender-v2.92-release' |
Revision 14f61c6 by Campbell Barton 1 hour 36 min ago |
Fix wm.context_* operators reusing values when it's not expected wm.context_* operators typically have their options set by menus or key bindings. Re-using options in this case can cause problems where two actions that change unrelated properties will re-use a setting from the previous execution. For example changing the lights Power impacted changing it's Radius afterwards. |
Revision 4fc54dd by Campbell Barton 1 hour 59 min ago |
Cleanup: spelling |
Revision 1559aa3 by Pablo Dobarro 2 hours 38 min ago |
Merge branch 'blender-v2.92-release' |
2 hours 40 min ago |
Fix T84031 initialize connectivity info of the base mesh before using Displacement Smear brush. Reviewed By: pablodp606 Maniphest Tasks: T84031 Differential Revision: https://developer.blender.org/D9956 |
Revision 93e3aed by Hans Goudey 5 hours 1 min ago |
Merge branch 'blender-v2.92-release' |
Revision aa030d3 by Hans Goudey 5 hours 3 min ago |
Fix: Unable to animate nodes modifier exposed properties The RNA path used for animating the settings passed to the node tree is incorrect. Currently it's just `settings.property_name`, but it's the path from the ID, not the modifier, so it should be `modifiers[modifier_name].settings.property_name`. However, the "Settings" struct is separated in RNA and DNA, which means that the callback to get the RNA path does not know about the modifier's name in order to fill the above path, so some reference to the modifier in the "Settings" struct would be necessary, which would create a convoluted layout in the `ModifierData` struct. Instead, this commit simply removes the "Settings" struct from RNA, which isn't as elegant from the point of view of the Python API, but otherwise it's a nice simplification. Note that we don't remove the "Settings" struct from DNA, because it would break reading old files. Differential Revision: https://developer.blender.org/D10175 |
Revision 51c433f by Ray molenkamp 6 hours 59 min ago |
Windows: Remove zero terminator from stack trace Important lesson to be learned here, leaving comments is great and in the moment, they usually make sense. Many months later they may not quite make as much sense any more and time will have to be spend to figure out what was meant, all of this would have been averted with a better comment. The zero terminator in this case, I can find no evidence of it being used or relied on at any point. It does however break GTests's `EXPECT_EXIT` macro that stops looking in the output as soon as it sees the zts and doesn't end up looking at the actual assert text being thrown. Which in turn makes the`fcurve_active_keyframe`test fail when run in debug mode on windows. |
Revision 8a77019 by Jacques Lucke 7 hours 24 min ago |
Cycles: modernize usage of rna iterators Using rna iterators in range-based for loops is possible since {rBc4286ddb095d32714c9d5f10751a14f5871b3844}. This patch only updates the places that are easy to update without more changes in surrounding code. Differential Revision: https://developer.blender.org/D10195 |
Revision 04f91bc by Brecht Van Lommel 7 hours 34 min ago |
Fix build error after Cycles Amembic procedural commit |
7 hours 58 min ago |
Cycles: internal support for Alembic procedurals The implementation is currently optimized to load animation sequences once and then quickly scrubbing through them. Later on an option should be added to optimize for memory usage and only load the current frame into memory. Currently mesh and curve objects are supported, including support for UV and vertex color attributes. Missing still is support for arbitrary attributes and motion blur, as well as better handling of changing topology. Shader assignments are made using FaceSets found in the Alembic archive. The animation (and constant) data of the objects inside the Alembic archive is loaded at once at the beginning of the render and kept inside a cache. At each frame change we simply update the right socket of the corresponding Cycles node if the data is animated. This allows for fast playback in the viewport (depending on the scene size and compute power). Note this is not yet exposed in the Blender UI, it's a feature that is still under development and not ready for general use. Ref T79174, D3089 |
7 hours 58 min ago |
Cycles: internal support for the concept of procedurals Procedurals are nodes in the scene that can generate an arbitrary number of other nodes at render time. This will be used to implement an Alembic procedural that can load an Alembic file into Cycles nodes. In the future we also expect to have a USD procedural. Direct loading of such files at render time is a standard feature in other production renderers. Reasons to support this are memory usage and performance, delayed loading of heavy scene data until rendering, Cycles standalone rendering using standard file formats beyond our XML files, and shared functionality for Cycles integration in multiple 3D apps. Ref T79174, D3089 |
8 hours 1 min ago |
Revision 2a81d94 by Bastien Montagne 9 hours 1 min ago |
LibOverride: refactor of relationships handling in library overrides. First step towards a better handling of relationships between IDs in override context, especially when a resync is needed. First, introduce a new flag to override operations, `IDOVERRIDE_LIBRARY_FLAG_IDPOINTER_MATCH_REFERENCE`, for ID pointers. It keeps track of whether an RNA ID pointer has been kept to its 'natural overriden ID' (in override hierarchy context), or has actually been re-assigned to some other data-block. Second, refactor how we deal with relationships between IDs in override hierarchy code, especially in resync case. This will fixe several cases listed in T83811, especially the case where an ID pointer to an existing override needs to be updated to a new one due to a matching change in linked data. |
Revision 5c490bc by Julian Eisel 9 hours 12 min ago |
Fix T85027: Crash dragging a collection over empty Outliner Filtering may make the Outliner tree empty. The function to find the drop element should just return null then and let the caller decide how to deal with it. |
|