Practical Info
This is a weekly video chat meeting for planning and discussion of development related to the sculpting and painting in Blender. Any contributor (developer, UI/UX designer, writer, …) working on these features in Blender is welcome to join and add proposed items to the agenda.
Write us a message in the module chat if you’re interested.
For users and other interested parties, we ask to read the meeting notes instead so that the meeting can remain focused.
- Upcoming Agenda
- Google Meet
- Time: Tuesday 6pm CET
- Next Meeting: December 20, 2022
- Module Chat
Attendees
- Joe Eagar
- Julien Kaspar
- Ramil Roosileht
- Daniel Bystedt
Agenda
High Priority Bugs
-
T102991 Regression: Sculpt: Fast Navigate does not work
Joe mentioned it could use different resolutions rather than the base. This would make it more useful visually.
But we should investigate the performance impact of this setting before improving it further -
Joe found 2 more bugs for dyntopo. Might be in 3.4. Joe fixed them but they need to be backported.
In Review
-
D16758 Sculpt: Vertex painting color textures
Added support for color textures for sculpt vertex painting.Joe mentioned that versioning code will flip texture & texture mask. But that might break brushes that are used in multiple modes?
That should be investigated.This also throws in the question the feature of shared brushes in multiple modes. Could become very useful for paint mode & sculpt mode?
-
D16511 Sculpt Mode: Resolve
Shift Rshortcut conflicts
Added adjustments for IC keymap. Waiting for accept from Aaron.The
Shift Alt Doperator for dyntopo detail size also turned out to be an old duplicate.
We should remove it and the shortcut. -
D16544 Sculpt Mode: Improvements to operators that rely on cursor position
Joe will review this. -
D16434 Sculpt Mode: Invert Expand behavior for masking consistency
Joe will review this.
Current Topics
-
T98070 Improved Rake functionality
Dyntopo refactor took some time recently. Joe will pivot back to roll mapping feature for now. -
T101593 Auto-Masking Popover for the Header
Various related tasks like T102971, T102585, T102437 & T102377.On T102971:
Brush properties refactor unified behavior works differently than this.
The question is if it’s a valid use case that brush settings can force the auto-masking to be disabled.
We should look into that.Recent feedback to limit the cavity masking default to half of the range to specifically target creases or peaks. This seems more useful.
We could change the curve by default. An extra slider to clip the curve is an option but undesirable by artists.Halved range is better but having “custom curve” enabled by default maybe not ideal.
It would at least make it clear that the range is halved by default but it does take more screen-space
and naming it “Custom” seems also wrong if it is enabled by default. -
T97352 3D texturing: Fix seam bleeding
Jeroen will spend time on finishing this task and boundary bleeding next.
Upcoming To Do’s
Joe:
- Finish patch for the Roll brush
- Wrapping up Auto-Masking tasks
- Afterwards, fully focus on Dyntopo refactor
Julien:
- Mask Icon Discussion
- Manual Introduction Pages
Daniel:
- Working with Julien to collect design thoughts for Layered Sculpting
Ramil:
- Will pick up bug reports to fix
- Will also communicate with Modeling Module about UV feature he wants to work on
Other Topics
How to communicate breaking changes in a new release?
We’ll soon make changes to the keymap, and there are always new releases with updated defaults.
Do we highlight this more prominently in the release notes?
Or does it make sense to add another page for breaking/important changes?
This could then generally include API, UI, tool defaults and shortcut changes that users should be aware about.
Ideally this would happen directly in Blender in some way but that seems intrusive and unlikely to be added.
This should be discussed more with the UI module or Pablo Vazquez.
Trim Tools & Project Tools
The current Trim and Project tools are not performant or useful enough.
But doing proper changes would need heavy reworking of the tools.
A better way of approaching the trim tools is to integrate them with the voxel remesher.
This would need to be less precise than exact boolean operations and could vastly increase performance.
Project tools could fair geometry instead of just snapping them . Assigning them a face set like the trim tools is also a good addition.
But we should prioritize this at some point fully to also add the full set of tools that is missing.
Community devs involvement
We need to make the module more open and inviting for devs to help out with small tasks.
At some point it’s worth going over the workboard to add more tasks as “Good first issues”.
Joe also points out that the incremental C++ refactor will contain a lot of low effort tasks that we could add there.
A bigger refactoring project for the sculpt and painting code would also in general help to reduce the complexity and learning curve for working in the module.
