June 22, 2021, 17:49 (GMT) |
Fix T89366: GPencil hide layers above parented layer The problem was the flag was not reset by layer in the loop. |
June 22, 2021, 17:43 (GMT) |
Pushed all thumbnail rendering and caching code to new function. Cleaned up all conditions using context->is_thumb. |
June 22, 2021, 17:19 (GMT) |
Fix T89343: Point cloud instances not transformed when realized This problem has surprisingly been there for quite a few months. For point clouds all attributes were handled the same, even "position", which should be transformed when combining source points into the destination. |
June 22, 2021, 17:13 (GMT) |
Revert "Enhanced stats/reports for blendfile reading." This change crashes library linking operators, related tests and probably more. This reverts commit f8d219dfd4c31a918e33cb715472d91a5cd3fd51. Ref D11583 |
June 22, 2021, 16:35 (GMT) |
Geometry Nodes: Join curve attributes when realizing instances Previously the code assumed that curve instances had no attributes. This is true when the data came from curve objects, which don't support attributes currently, but it isn't necessarily true when retrieving curves from evaluated geometry sets. |
June 22, 2021, 16:32 (GMT) |
Cleanup: Refactor spline copying functions Make the virtual functions protected and simpler, so that the logic is better contained in the base class's implementation. Also introduce a `copy_without_attributes` method to be used for realizing instances. |
June 22, 2021, 16:26 (GMT) |
Fix deadlock with shrinkwrap and other modifiers More code that needs task isolation. Encountered in sprite fright production file. Ref D11603 |
June 22, 2021, 16:19 (GMT) |
adaptive_cloth: mesh_reader: obj parse |
June 22, 2021, 15:28 (GMT) |
Enhanced stats/reports for blendfile reading. Add direct user feedback (as a warning report) to user when recursive resync of overrides was needed. And some timing (as CLOG logs) about main readfile process steps. This is essentially adding a new BlendFileReadReport structure that wraps BKE_reports list, and adds some extra info (some timing, some info about overrides and (recursive) resync, etc.). |
June 22, 2021, 15:09 (GMT) |
Organize USD and Alembic conditional includes. Grouped common USD and Alembic mesh sequence cache code includes. |
June 22, 2021, 15:04 (GMT) |
LineArt: Move type rejection before visibility check |
June 22, 2021, 15:03 (GMT) |
LineArt: Move type rejection before visibility check |
June 22, 2021, 15:02 (GMT) |
Minor cleanup to previous commit introducing `BLI_math_time`. Forgot to address latest review comments, sorry for the noise.`:wq |
June 22, 2021, 15:00 (GMT) |
Add initial `BLI_math_time` with a 'seconds decompose' function. Allows to decompose a given amount of seconds into a random set of days/hours/minutes/seconds/milliseconds values. Also add matching test. Differential Revision: https://developer.blender.org/D11581 |
June 22, 2021, 13:43 (GMT) |
Animation: allow specifying a custom frame range for actions. Some operations, e.g. adding a new action strip to NLA, require knowing the active frame range of an action, but currently it can only be deduced by scanning the keyframes of the curves within it. This is not ideal if e.g. curves are staggered for overlap. As suggested by Nathan Vegdahl, this patch adds Action properties that allow manually specifying its active frame range, and whether it is intended to be cyclic. The settings are exposed in a popover in Action Editor. When enabled, the range is highlighted in the background using a striped fill to distinguish it from the solid filled regular playback range. When set, the frame range is used by NLA. In addition, the Cycle-Aware Keying option automatically sets up F-Curves newly added to a cyclic action to use cyclic extrapolation with the correct period. |
June 22, 2021, 13:43 (GMT) |
Animation: support filtering for curves with a cycle period mismatch. Since the looping behavior is defined per curve rather than at action level, it is possible for curve loop periods to get out of sync with each other. This commit adds an option to compare curves against the frame range specified in the action, and treat those with a mismatch as errors for the purpose of F-Curve filtering. When enabled, the check verifies that curves within the action have valid cyclic extrapolation, and the action period evenly divides by the curve period (since a curve looping at e.g. half of the action period length still repeats in sync with the action). |
June 22, 2021, 13:43 (GMT) |
Temporary Hack: provide B-Bone scale versioning for files with old patch. Run the versioning code for the conversion of bbone scale to an xyz vector if it has fields that correspond to the old version of the patch before that change requiring versioning. The actual Y (length) scale value from the old patch isn't versioned and will be lost, requiring manual fixing. |
June 22, 2021, 13:43 (GMT) |
Bone Overlay: support bone wireframe opacity settings. When weight painting the bone overlay is extremely intrusive, effectively requiring either extensive use of hiding individual bones, or disabling the whole bone overlay between selections. This addresses the issue by adding two bone opacity sliders that are used for the 'wireframe' armature drawing mode. One directly controls the opacity in a uniform way. The other one allows fade based on the depth between the near and far clip planes in order to provide an automatic visual cue about which bones are closest. |
June 22, 2021, 13:43 (GMT) |
Constraints: refactor the D7437 patch adding Custom Space for constraints. As mentioned in the comments to that patch, I had an idea for a different way to do some technical aspects, but it was too complicated to force changes in the original patch. Thus I submit this follow up patch. First, instead of modifying all the get_constraint_targets and flush_constraint_targets callbacks, introduce wrapper functions for accessing constraint targets, convert all code to use them, and handle the new reference there uniformly for all constraints. This incidentally revealed a place in the Collada exporter that didn't clean up after retrieving the targets. Also, tag the special target with a flag so other code can handle it appropriately where necessary. This for instance allows dependency graph to know that the Use B-Bone Shape option doesn't affect this specific target. Finally, rename and simplify the function for initializing the custom space, and make sure it is called everywhere necessary. Differential Revision: https://developer.blender.org/D9732 |
June 22, 2021, 13:43 (GMT) |
Constraints: support a new Local Space (Owner Orientation) for targets. Add a new transformation space choice for bone constraints, which represent the local transformation of the target bone in the constraint owner's local space. The use case for this is transferring the local (i.e. excluding the effect of parents) motion of one bone to another one, while ignoring the difference between their rest pose orientations. Owner Local Space replaces the following setup: * A `child` bone of the `target`, rotated the same as `owner` in rest pose. * A `sibling` bone of the `target`, positioned same as `child` in rest pose and using Copy Transforms in World Space from `child`. * The `owner` bone constraint uses Local Space of `sibling`. (This analogy applies provided both bones use Local Location) Since the space list is getting long, also add a couple of separators. Differential Revision: https://developer.blender.org/D9493 |
|
|
|


Master Commits
MiikaHweb | 2003-2021