1. 27 Dec, 2021 1 commit
  2. 22 Dec, 2021 1 commit
  3. 21 Dec, 2021 1 commit
    • Sybren A. Stüvel's avatar
      Fix T94264: Pose Library, doubleclick-to-apply only in asset browser · c08568cc
      Sybren A. Stüvel authored
      Fix a keymap collision between the pose library and the file manager.
      Only allow `applying a pose by doubleclicking it in the asset browser, and
      not in the file browser. This prevents a crash; appending an Action
      would temp-load it in order to apply it as a pose, which of course
      conflicts with the "Append" functionality.
  4. 18 Dec, 2021 3 commits
  5. 17 Dec, 2021 1 commit
  6. 16 Dec, 2021 1 commit
    • Sybren A. Stüvel's avatar
      New animation add-on: Copy Global Transform · d737f201
      Sybren A. Stüvel authored
      This add-on allows animators to copy the global transform of the active
      object or pose bone onto the clipboard. It can then be pasted in three
      different ways:
      - To the current transform of the selected object/pose bone (could be a
        different one than was used for the copying).
      - To selected keyframes.
      - Baking to all frames between the first and last selected keyframe
        (defaulting to preview range or scene range).
      All three methods are compatible with auto-keying.
      The latter two methods *require* auto-keying to be enabled, to give the
      animator control over which keying set to use, etc.
      An earlier version of this add-on was used by the Blender Animation
      Studio during Sprite Fright. Since then the two paste-to-frame-range
      options were added, by request of the animators.
      Reviewed by: campbellbarton
      Differential Revision: https://developer.blender.org/D13570
  7. 14 Dec, 2021 1 commit
    • Demeter Dzadik's avatar
      Rigify: Clean up "Rigify Buttons" panel UX · ece39d80
      Demeter Dzadik authored
      The overall goal of this patch is to improve the UI/UX of the panel previously known as "Rigify Buttons" which presumably takes its name from the old "Buttons Panel" which is now known as the Properties Editor.
      - Make Rigify less reliant on name matching when it comes to maintaining the link between the metarig, the UI script, the generated rig, and the widgets collection. (Use pointers only, names shouldn't matter!)
      - Change the "Advanced" toggle button into a real sub-panel.
      - Split up the "Rigify Buttons" panels into "Rigify Generation" and "Rigify Samples" panels in non-edit and edit mode respectively, to better describe what the user will find there.
      Changes in the Rigify Buttons panel:
      - Removed the "overwrite/new" enum.
      	- If there is a target rig object, it will be overwritten. If not, it will be created.
      	- If a rig object with the desired name already existed, but wasn't selected as the target rig, the "overwrite" option still overwrote that rig. I don't agree with that because this meant messing with data without indicating that that data is going to be messed with. Unaware users could lose data/work. With these changes, the worst thing that can happen is that your rig ends up with a .001 suffix.
      - Removed the "rig name" text input field. Before this patch, this would always rename your rig object and your rig script text datablock, which I think is more frustrating than useful. Now you can simply rename them after generation yourself, and the names will be kept in subsequent generations.
      - Single-column layout
      - Changed the "Advanced Options" into a sub-panel instead.
      On request:
      - Added an info message to show the name of the successfully generated rig:
      Feedback welcome.
      Reviewed By: angavrilov
      Differential Revision: https://developer.blender.org/D11356
  8. 07 Dec, 2021 1 commit
    • Peter Kim's avatar
      Fix T93509: Unintended navigation on Valve Index · c60fef38
      Peter Kim authored
      The input bindings for "grab" navigation on the Valve Index controllers
      could previously trigger the action even when the user did not intend
      to do so (i.e. their hand was not actively gripping the sensor). This
      was resolved by changing the bindings from "/input/squeeze/value" to
      "/input/squeeze/force" and increasing the input threshold from 0.3 to
      Thanks to sybren for testing.
  9. 01 Dec, 2021 2 commits
  10. 29 Nov, 2021 4 commits
  11. 25 Nov, 2021 3 commits
  12. 24 Nov, 2021 4 commits
  13. 23 Nov, 2021 4 commits
  14. 22 Nov, 2021 5 commits
  15. 19 Nov, 2021 3 commits
  16. 18 Nov, 2021 4 commits
  17. 16 Nov, 2021 1 commit