October 6, 2021, 10:08 (GMT) |
EEVEE: Fix double Stroke color in Panel The stroke color was displayed in the side panel and this must be used only in 3D View. |
Revision 6f6e33e by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Animation: support filtering for curves that don't match the action cycle. 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 any mismatches as errors for the purpose of F-Curve filtering. When enabled, the check verifies that curves within the action have valid cyclic extrapolation, 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), and the end values match if the cycle is supposed to be perfect. Differential Revision: https://developer.blender.org/D11803 |
Revision 1e6de47 by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Force Fields: implement new true power and custom falloff options. The 'power' falloff option in Blender force fields does not actually generate a true power falloff function, as pointed out in D2389. However, that patch adds a special 'gravity' falloff option to Force fields, without addressing the shortcoming in the common options. The reason for not using the true curve in the options, as far as one can tell, is that the power curve goes up to infinity as the distance is reduced to 0, while the falloff options are designed so that the maximum value of the curve is 1. However, in reality forces with a power falloff don't actually go to infinity, because real objects have a nonzero size, and the force reaches its maximum at the surface of the object. This can be used to integrate an option to use a true power falloff with the design of falloff settings, if it requires a nonzero 'minimum' distance to be set, and uses a curve that reaches 1 at that distance. Since this is adding a new feature to the minimum distance value, it is also a good opportunity to add a feature to the maximum distance. Specifically, the new options can be used to apply arbitrary brush-style falloff curves between min and max, including a fully custom curve option. When used together with power falloff, the two curves are multiplied together. While the true power option allows creating more physically correct forces, the custom curves aid artistic effects. Differential Revision: https://developer.blender.org/D8075 |
Revision 332b9ee by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Depsgraph: connect up drivers on various physics properties. It seems drivers for physics properties weren't being linked to evaluation nodes. This connects settings used by modifiers to Geometry; particle settings and rigid body data to Transform which seems to contain rigid body evaluation; and force fields to object Transform, since fields can exist on empties. Differential Revision: https://developer.blender.org/D10088 |
Revision 5abdc50 by Alexander Gavrilov October 6, 2021, 09:49 (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 |
Revision eb8cda5 by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Armature: apply Y scale to B-Bone segments. This fixes a strange behavior where the segments were not actually scaled in the Y direction to match their actual length, thus producing gaps or overlap depending on the shape of the curve. For transformation the change should be very small if enough segments are used, but this will affect the results of the Copy Transforms and Armature constraints, so a backwards compatibility option is provided. Newly created bones default to the new behavior. |
Revision 1ae4319 by Alexander Gavrilov October 6, 2021, 09:49 (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. |
Revision db0715e by Alexander Gavrilov October 6, 2021, 09:49 (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 uniform opacity as the straightforward option. The other one allows fade based on the depth from the camera, using exponential decay with the slider specifying the 'half-life' depth. This is intended as a way to automatically hide bones in distant parts of the mesh while focused on a specific part. Differential Revision: https://developer.blender.org/D11804 |
Revision b616f3c by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Context: add accessors returning selected actions for animation editors. Add a new 'selected_visible_actions' property to allow querying actions that are selected in animation related editors for use in UI and operators. The 'selected_editable_actions' variant excludes linked actions (the only reason an action can be read-only). In the Action and Shape Key editors there is only one action that is specified by the field at the top of the editor. In Dope Sheet it scans the channel rows and returns all actions related to the selected items. This includes summary items for actions and groups. In Graph Editor, it lists actions associated with selected curves. The new property is also used for Copy To Selected and Alt-Click. Ref D11803 |
Revision 59233cd by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Animation: allow manually setting the intended playback range for actions. Some operations, e.g. adding a new action strip to NLA, require knowing the active frame range of an action. However, 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 in comments to T54724, this patch adds Action properties that allow manually specifying its active frame range. The settings are exposed via a panel in the Dopesheet and 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 when adding or updating NLA tracks, and by add-ons using `Action.frame_range`, e.g. FBX exporter. Differential Revision: https://developer.blender.org/D11803 |
Revision 14fda3c by Alexander Gavrilov October 6, 2021, 09:49 (GMT) |
Animation: allow marking actions as cyclic for Cycle-Aware Keying. When a manual frame range is set, allow marking an action as having Cyclic Animation. This does not affect how the action is evaluated, but the Cycle-Aware Keying option will automatically make any newly added F-Curves cyclic. This allows using the option from the start to build the cycle, rather than only for tweaking an existing loop. The curves are made cyclic when they have only one key, either after inserting the first key, or before adding the second one. The latter case avoids the need to manually make the first added curve cyclic after marking a newly added action cyclic. Differential Revision: https://developer.blender.org/D11803 |
Revision 330dc8b by Alexander Gavrilov October 6, 2021, 09:48 (GMT) |
Python API: implement `PoseBone.children` via `Bone.children`. Currently `PoseBone.children` is implemented by a linear scan of the list of armature bones. This is doubly inefficient, since not only is it scanning all bones, the `obj.data.bones` list is actually synthetic and generated from Bone children lists. Instead, use the `Bone.children` native RNA property. Differential Revision: https://developer.blender.org/D12727 |
October 6, 2021, 09:43 (GMT) |
Fix handling of overrides during append. Liboverride references need a special handling during append, since those pointers should never be made local, nor reampped to newly localized data. And liboverride references should never be directly made local either, to ensure their liboverride usages remain pointing to linked data and not local one. Issue was reported by the studio, and also probably as part of T91892. |
October 6, 2021, 09:24 (GMT) |
Fix possible use-after-free when cancelling temporary rename button If a renaming button was removed via `UI_but_active_only_ex()` and that button was placed using the layout system, the button was still in the layout. So far this didn't cause issues, because all cases where the button may be removed were not using the layout system. |
Revision 9d216ef by Charlie Jolly / Dalai Felinto (temp-geometry-nodes-delete-geometry-image-texture) October 6, 2021, 08:55 (GMT) |
Geometry Nodes: Add Image texture node (WIP) Port shader image texture node **Core devs: Please take over if you want to.** {F10797876} Differential Revision: https://developer.blender.org/D12734 |
October 6, 2021, 08:46 (GMT) |
Sculpt: fix broken ray casting of original data in pbvh Not sure if this ever worked. |
October 6, 2021, 08:35 (GMT) |
Revert python changes in material panel |
October 6, 2021, 08:25 (GMT) |
Fix T91064: Cycles low poly meshes having black edges when shade smoothed Fixes:{T91064} Caused by {rBcd118c5581f482afc8554ff88b5b6f3b552b1682} - Applies `ensure_valid_reflection()` to the normal input on all BSDFs for CPU and GPU. - This doesn't affect hair. - Removes `ensure_valid_reflection()` from the output of Bump Map and Normal Map nodes for CPU/GPU as it is not needed. - The fix doesn't touch OSL. Reviewed By: brecht, leesonw Maniphest Tasks: T91064 Differential Revision: https://developer.blender.org/D12403 |
October 6, 2021, 07:12 (GMT) |
October 6, 2021, 07:01 (GMT) |
Sequencer: improvements to preview selection - Support toggle/deselect/deselect_all options (matching 3D viewport object selection). - Support legacy selection behavior. - Support selecting by the center in preview views (holding Ctrl). |
|
|
|


Master Commits
MiikaHweb | 2003-2021