Date/Time: 2023-12-04T15:00:00Z
Link: https://meet.google.com/xxo-tyin-rem
Attendees :
- Amélie Fondevilla (LFS, Developer)
- Antonio Vazquez (Developer)
- Casey Bianco-Davis (Developer)
- Falk David (Blender developer)
- Matias Mendiola (Grease Pencil core team)
- Nick Fox-Gieg (York University)
- Samuel Bernou (ADV Studio, Python dev)
Topics
- Development updates
Meeting Notes
- Development updates
- Antonio worked on many material related operators (#115278: GPv3: Lock unselect materials operator, #115041: GPv3: Lock and Unlock all materials operators, etc.).
- Casey worked on the duplicate points operator in edit mode and also fixed the overlays to hide points in locked layers.
- Falk fixed an issue in the draw operator that made it feel very laggy and sluggish. Also worked on #115602: GPv3: Drawing Placements and rendering GPv3 to an image.
Show all commits
- Fix: GPv3: Stutter while drawing by Falk David
- GPv3: Material locking by Falk David
- GPv3: Replace depsgraph tag to ID_RECALC_GEOMETRY by Antonio Vazquez
- GPv3: Avoid unnecessarily creating cyclic attribute in hard erasor by Hans Goudey
- Fix: GPv3: Missing curve type counts update in hard erasor by Hans Goudey
- GPv3: Lock Unused Materials operator by Antonio Vazquez
- GPv3: Lock and Unlock all materials operators by Antonio Vazquez
- GPv3: Hide Others operator by Antonio Vazquez
- Fix: GPv3: Uninitialized runtime variable by Falk David
- Fix: GPv3: Wrong location in
paint_init_pivot
by Falk David - GPv3: Lock unselect materials operator by Antonio Vazquez
- GPv3: Fix #113994: Overlay: Hide points for locked layers. by casey bianco-davis
- Fix: GPv3: Smoothing even with factor of 0 by Falk David
- GPv3: “Set Active Layer” operator and menu by Clément Busschaert
- GPv3: Duplicate Points operator by casey bianco-davis
- GPv3: Show and hide layers operators by Matias Mendiola
- GPv3: Menu to Select Material using
U
key by Antonio Vazquez - GPv3: Fix compiler warning and format by Antonio Vazquez
- Notes of a rendering meeting (2023-11-21, Brecht, Clément, Falk):
- We discussed four major points:
-
- Is there a good reason for having a separate renderer for Grease Pencil ? Is this similar to the question “how do we do NPR rendering in Blender” ?
- Yes. There is an ongoing discussion with dillongoo studios about NPR rendering in Blender. There is a possibility that an NPR engine would render grease pencil as well, thus replacing the current renderer. Everyone agreed that having a separate engine for grease pencil is limiting and we should find a better solution.
-
- Anti-aliasing issue
- Clément: This can be solved similarly to how the workbench engine deals with aliasing. Some “jittering” approach could be implemented. This would be likely for after GPv3 is completed.
-
- Batch cache for rendering performance issue
- Passing the attributes directly is possible, but would require some rewrites of the engine.
-
- Triangulation for rendering issue
- It’s unclear if this is a bottleneck - would have to be investigated further.
- Nick: Doesn’t the Geometry Node support already allow us to ‘render’ grease pencil in other engines?
- Falk: Technically yes, but it requires meshing the curves and then assigning a material. Grease Pencil can currently be rendered without the need for meshing. It’s all done in the shader. So that is much faster.
- Casey: GPv2 has the ability to edit strokes using bézier curves. Will GPv3 also have this functionality?
- Falk: One of the reasons we chose
CurvesGeometry
as the fundation for GPv3 was that it also is able to represent other types of curves and not only poly curves. Whether or not we can have this functionality in GPv3 is unclear. It’s not used as much so we might consider leaving it for a later release. That being said, the goal is to have native bézier support for grease pencil and the data-structure allows for it.
- Falk: One of the reasons we chose
Next Meeting
- Time/Date: 2023-12-18T15:00:00Z
- Link: 2023-12-18 Grease Pencil Module Meeting
- Agenda:
TODO