The meeting will be on 2025-02-27T17:00:00Z. It is open for everybody interested to join the video call (link below).
Present: Andy Beers, AnimSebs (Dillon Goo Studios), Christoph Lendenfeld, David Woolf, Jeremy Bots, Jorn Boven, Julien Duroure, MohammadHossein Jamshidi, Nate Rupsis, Nathan Vegdahl, Nitin Rawat, Raymond Luc
People present are referred to by first name for brevity. Others are referred to by full name.
Links
- Video Call
- A&R Module Meetings calendar for inclusion in your own calendar app
- Previous & next meeting notes
- Long Term Plans & Current Focus
- Issues & Pull Requests
- #module-animation chat channel
- Draft agenda for any upcoming meetings
Opening
- Please raise your hand when you donât understand things for any reason. The purpose of these meetings is collaboration. It is absolutely fine to ask for explanations.
- There are no recordings of the meeting. This way everybody is free to say or show anything they want.
Landed
Names are from the Git log. This list is limited to functional improvements & bugfixes.
Blender
- 0bb750ee844: Fix: #134636: VSE - Fade In and Out not working (Sybren A. StĂźvel) (2025-02-20)
- 3dbede128eb: Fix #134581: Regression: Animation breaking going from 4.3 to 4.4 (Sybren A. StĂźvel) (2025-02-20)
- d6da9710d0e: Modeling: Support normalization with locked vertex groups in N-panel (Andy Beers) (2025-02-21)
- 981e06f3bd2: Fix #134758: renaming a node breaks animation (Christoph Lendenfeld) (2025-02-21)
- 857743db9d6: USD: import skeletal animation as slotted Actions (Sybren A. StĂźvel) (2025-02-24)
- 3fd430d1c6b: Anim: make
BKE_fcurves_id_cb()
only report F-Curves for that ID (Sybren A. StĂźvel) (2025-02-24) - ba149680a24: Fix #134810: animating Grease Pencil layer âhideâ option doesnât un-hide (Sybren A. StĂźvel) (2025-02-25)
- 5100a80f7f7: Fix #110650: Drivers not removed if removing their container (Christoph Lendenfeld) (2025-02-25)
Ongoing Work
- High Prio bugs:
- Christoph:
- Christophâs weekly report
- abandoned fixing #134845: Fix #131493: Playhead jumping when changing FPS during playback with audio sync due to work being done in the area.
- trying to fix #113794: Driver Values change after move order of Node Group Input
- various other bugfixes
- Nathan:
- Nathanâs weekly report
- Worked on fixing a long-time bug in the Action Editor / Dopesheet that slotted actions made more obvious: #134746: Action Editor Action Slot âsummaryâ shows keyframes of hidden bones (Fix: #134922)
- Now continuing work on Blender Variables (not animation/rigging related).
- Sybren:
- Animator meeting at Blender HQ, with Rik Schutte, Hjalti HjĂĄlmarsson, and Pablo Fournier:
- Rik made #135062: Auto Normalize functionality for vertex groups (edit mode) and weightpaint operators (weightpaint mode).
- Shift-G in pose mode: missing options that are in Object mode
- Select Children
- Select Immediate Children
- Select Siblings
- Select Parent
[
/]
in pose mode: trying to do too much at once- #134503: Improvements to bones âSelect Child/Parentâ hierarchy
- Selecting all children: should be under a modifier key like âshiftâ.
- Expanding selection or not: now handled by âshiftâ, could be another modifier key.
- For âwalking the active boneâ: a âselect next/previousâ sibling should be added
- Should be predictable what is the âsibling orderâ, like alphabetical, or alphabetical + prioritizing connected bones. This then determines the âwalk to next/prev siblingâ, but also which bone is selected with âwalk to childâ.
Playback Behavior With Scene Frame Range
Sebastian Parborg has been working on fixes with audio-synced playback. While testing, he noticed something odd but unrelated to audio sync:
When you start playback with the frame head earlier than the start frame, playback first jumps to the start frame. However, if during playback you scrub to earlier than the start frame, then playback continues from there without jumping to the start frame. This feels inconsistent, and it seems like we ought to have one consistent behavior for both cases. Which behavior makes more sense?
- Nathan: note that you can still play outside of the scene frame range if desired by using the preview range feature.
- Ray: thinks it should snap to the start frame.
- Module agrees.
- Decision: always snap to be within the set frame range during playback, including when scrubbing during playback.
Selecting F-Curves in the Graph Editor
Context: #43933 - Graph Editor: (Auto-)Focusing Channels - blender - Blender Projects
With box select, when you overlap with a curve but no keys, the whole curve is selected. When you click-select on a non-key part of a curve, however, nothing happens.
- Question 1a: is the box-select behavior useful as-is?
- Jeremy: use it for global adjustments.
- Ray: what Jeremy said, and also to quickly select a visible curve (sometimes easier/faster than using the channel list) and shift-h to isolate it.
- Consensus: yes, this is very useful.
- Question 1b: would it make more sense for it to select the curve without selecting the keys?
- Nate and Animsebs: what would be the use case for selecting the curve without the keys?
- Nathan: maybe if you already have keys selected, and you just want to shift-h isolate the curve without losing your key selection? Seems niche, though, and not the common case.
- Consensus: better to select all the keys as well.
- Question 2: should click-select follow the same behavior, for consistency?
- Tons of thumbs up.
- Ray: I currently work around the lack of this by selecting a key, and then hitting L.
- Consensus: yes, it should.
- Decision: box select should keep its current behavior, and click-select should be updated match (so clicking on a non-key part of an f-curve selects the whole curve).
Splitting Up PRs, and Where to Ask Dev Questions
- Andy: I have questions about how and if I should split up an issue into multiple PRs. Where should I ask questions about this (in the chat, in the issue, âŚ)?
- Nathan: always feel free to ask development questions in the chat. Itâs a development channel, and thatâs what itâs for.
- If the questions are specific to a particular issue or PR, you can also ask in the chat, but if you want to keep the discussion in the issue or PR (which is often a good idea) then you can post there.
- Also, always feel free to poke us in the chat with an @ if you want to make sure we see something (regardless of whether that something in an issue/PR or in the chat itself).
- Christoph: regarding splitting up an issue into multiple PRs, sometimes itâs not clear ahead of time if/how something should be split up. In such cases, feel free to just dive in with a single PR, and then you can split it up later as things become clearer through actually coding the thing. We do this all the time.
Next Meeting
The next meeting will be on 2025-03-06T17:00:00Z. Again it will be open for everybody whoâs interested. The provisionary meeting agenda will be updated before the meeting.