WIP: GPv3: Geometry-based Fill tool #114318

Draft
Sietse Brouwer wants to merge 39 commits from SietseB/blender:gp3-vector-fill into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Member

Work in progress
This is an experimental attempt to implement a vector-based Fill tool
for GPv3. Vector-based means: using the actual points of the edge
strokes, instead of creating new, unrelated geometry points as the
GPv2 flood-fill algorithm does.

_Work in progress_ This is an experimental attempt to implement a vector-based Fill tool for GPv3. Vector-based means: using the actual points of the edge strokes, instead of creating new, unrelated geometry points as the GPv2 flood-fill algorithm does.
Sietse Brouwer added 21 commits 2023-10-31 12:10:02 +01:00
Sietse Brouwer added this to the Grease Pencil project 2023-10-31 12:10:52 +01:00
Sietse Brouwer reviewed 2023-10-31 12:45:50 +01:00
Sietse Brouwer left a comment
Author
Member

@antoniov I added some notes to give you a starting point for exploring the 'gap closure' code I used for the Fill tool.

@antoniov I added some notes to give you a starting point for exploring the 'gap closure' code I used for the Fill tool.
@ -0,0 +3266,4 @@
}
/* Convert curves to viewport 2D space. */
vf->curves_2d = curves_in_2d_space_get(&vf->vc, vf->vc.obact, drawings, layer_indices, true);
Author
Member

Here a set of GP drawings (layers) is converted to viewport 2D space. The function is declared in editors\include\ED_grease_pencil.hh and defined in editors\grease_pencil\intern\grease_pencil_utils.cc.

In the curves_2d structure all curves of all layers are packed together and accessible through offset indices. E.g. looping over all first and last points of all curves goes this way:

for (const int curve_i : vf->curves_2d.point_offset.index_range()) {
  const int point_first_index = vf->curves_2d.point_offset[curve_i];
  const float2 co_first = vf->curves_2d.points_2d[point_first_index];

  const int point_last_index = vf->curves_2d.point_offset[curve_i] + vf->curves_2d.point_size[curve_i] - 1;
  const float2 co_last = vf->curves_2d.points_2d[point_last_index];
}

Relevant functions for gap closure by stroke end radius are:
init_curve_end_radii()
get_connected_curve_end_radii()

For gap closure by extending the stroke ends:
init_curve_end_extensions()
get_curve_end_extensions()

The drawing of the gap lines in the viewport is done in:
draw_overlay()

Here a set of GP drawings (layers) is converted to viewport 2D space. The function is declared in `editors\include\ED_grease_pencil.hh` and defined in `editors\grease_pencil\intern\grease_pencil_utils.cc`. In the `curves_2d` structure all curves of all layers are packed together and accessible through offset indices. E.g. looping over all first and last points of all curves goes this way: ``` for (const int curve_i : vf->curves_2d.point_offset.index_range()) { const int point_first_index = vf->curves_2d.point_offset[curve_i]; const float2 co_first = vf->curves_2d.points_2d[point_first_index]; const int point_last_index = vf->curves_2d.point_offset[curve_i] + vf->curves_2d.point_size[curve_i] - 1; const float2 co_last = vf->curves_2d.points_2d[point_last_index]; } ``` Relevant functions for gap closure by stroke end **radius** are: `init_curve_end_radii()` `get_connected_curve_end_radii()` For gap closure by **extending** the stroke ends: `init_curve_end_extensions()` `get_curve_end_extensions()` The drawing of the gap lines in the viewport is done in: `draw_overlay()`
Member

I'm just scanning over the code to get an initial idea. Looks like you put a lot of thought into this!
One thing that I'm seeing is that you're using float2 for your 2d coordinates. And I can see that you're also having to do lots and lots of epsilon checks because of the precision issues.
Since we're already in screen space, I would advise to use int2 for the coordinates instead. That allows for precise intersection checks, without having to deal with floating point arithmetic.
Amelie ended up taking that same route for the eraser.

I'm just scanning over the code to get an initial idea. Looks like you put a lot of thought into this! One thing that I'm seeing is that you're using `float2` for your 2d coordinates. And I can see that you're also having to do lots and lots of epsilon checks because of the precision issues. Since we're already in screen space, I would advise to use `int2` for the coordinates instead. That allows for precise intersection checks, without having to deal with floating point arithmetic. Amelie ended up taking that same route for the eraser.
Sietse Brouwer added 4 commits 2023-11-16 15:49:42 +01:00
Sietse Brouwer added 1 commit 2023-11-16 20:03:58 +01:00
Sietse Brouwer added 1 commit 2023-11-16 20:51:06 +01:00
Antonio Vazquez added 1 commit 2023-11-16 22:48:32 +01:00
e5f41d40d2 Test commit
Just to test the git commit is working
Antonio Vazquez added 2 commits 2023-11-23 13:47:26 +01:00
30102eddca Merge branch 'main' into gp3-vector-fill
Conflicts:
	source/blender/editors/grease_pencil/intern/grease_pencil_ops.cc
	source/blender/editors/grease_pencil/intern/grease_pencil_utils.cc
	source/blender/editors/include/ED_grease_pencil.hh
b4b1caf5c5 GPv3: Fix errors after merge
Some include files changed.
Antonio Vazquez added 1 commit 2023-11-26 10:43:44 +01:00
Sietse Brouwer added 8 commits 2024-03-25 20:21:47 +01:00
Sietse Brouwer changed title from WIP: GPv3: Vector-based Fill tool to WIP: GPv3: Geometry-based Fill tool 2024-03-25 20:23:41 +01:00
This pull request has changes conflicting with the target branch.
  • scripts/startup/bl_ui/properties_paint_common.py
  • source/blender/editors/grease_pencil/intern/grease_pencil_ops.cc
  • source/blender/editors/grease_pencil/intern/grease_pencil_utils.cc
  • source/blender/editors/include/ED_grease_pencil.hh

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u gp3-vector-fill:SietseB-gp3-vector-fill
git checkout SietseB-gp3-vector-fill
Sign in to join this conversation.
No reviewers
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#114318
No description provided.