Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Porting Patches #1401

Open
jlampel opened this issue Jan 7, 2025 · 0 comments
Open

Porting Patches #1401

jlampel opened this issue Jan 7, 2025 · 0 comments
Assignees
Labels
question tool: patches v4 Applies to RF version 4x
Milestone

Comments

@jlampel
Copy link
Member

jlampel commented Jan 7, 2025

Patches is a great tool that allows for filling large areas with a grid of quads. Most importantly, it uses face nearest snapping rather than screen space snapping and works well even in areas that are partially occluded.

image

The main thing it's doing though is just a bridge or grid fill and then snapping the result to the surface. It cannot be used to draw new geometry from scratch, and it cannot be used when the result is not a perfect grid.

My thought for this one is that we could potentially skip it for the initial v4.0 release and bring it back in a different way in a later update. I have a few ideas for how Patches could be supercharged and more useful as a standalone tool, but for now I think we could get by with creating an operator that just fills an area depending on the type of selection and snaps the result (#1400). The other basic use cases are already handled well by Strokes, albeit in screen space.

In the short term, we would lose the ability to select which verts are considered as corners and to do some specific actions with face nearest snapping, but in the long term it frees us up to rethink how the tool works and to do much more interesting things with it in the future.

But I'm still kind of on the fence because I don't know how often this tool gets used. I personally don't use it a whole lot, but not everyone works the same as I do. I also don't know if porting it as-is would be a short task or a long one. If it's pretty easy and would just take an afternoon, it certainly wouldn't hurt, but I don't think it's worth holding up a release for a few weeks.

What do you think @vxlcoder, how much time would you estimate it would take to port Patches as-is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question tool: patches v4 Applies to RF version 4x
Projects
None yet
Development

No branches or pull requests

2 participants