# 2022-8-17 Sculpt/Texture/Paint Module Meeting

## Attendees

- Joe Eagar
- Julien Kaspar
- Daniel Bystedt
- Artur Mello Lattaro

## Agenda

### Needs Commit

None :+1:

### High Prio Bugs

- [⚓ T99288 Color attributes of index above 7 deletes after entering edit mode](https://developer.blender.org/T99288)
- Hans & Joe are working on it
- Joe will get on that asap
- [⚓ T98889 Regression: Sculpting on a linked copy of an objects crashes Blender](https://developer.blender.org/T98889)
- Relies on [⚙ D15428 PBVH Draw Cleanup](https://developer.blender.org/D15428)
- Can we get a temporary fix for 3.3 LTS?
- Sadly not
- [⚓ T99282 Regression: Object invisible in Sculpt Mode when using >8 color attributes](https://developer.blender.org/T99282)
- Also depending on PBVH Draw Cleanup

### In Review

- [⚙ D15428 PBVH Draw Cleanup](https://developer.blender.org/D15428)
- High priority for 3.4
- Needs a from scratch rewrite
- [⚙ D15596 Convert Color Attribute operator](https://developer.blender.org/D15596)
- No update from Ramil yet
- Joe raied concerns on converting sRGB color atrrbiutes. Will chek if there are any bugs currently.
- [⚙ D15025 Expose Face Sets In Python API](https://developer.blender.org/D15025)
- Any update Joe?
- Will target this for 3.4
- [⚙ D14900 PBVH Texture Paint Node Splitting](https://developer.blender.org/D14900)
- On hold for until further planning on Paint Mode?
- Would be best to already commit soon sais Joe
- [⚙ D15298 Support Automasking For Texture Paint](https://developer.blender.org/D15298)
- On hold for until further planning on Paint Mode?
- Will check with Jeroen/Dalai on planning for Paint Mode project
- [⚙ D15496 Sculpt Attribute API](https://developer.blender.org/D15496)
- Nothing marked as Done
- This should be a high priority

### In Progress

Targeted for 3.4 release. Deadline for Bcon2 = September 27

- [⚙ D15122 Cavity Automasking Mode](https://developer.blender.org/D15122)
- Still needs feedback adjustments. See comments.
- Also relies on D15496
- Julien can provide more detailed mockup to resolve UI issues
- Daniel provided feedback
- Havin both brush and mode cavity on can be very confusing
- [⚙ D15297 Normal Based Automasking Modes](https://developer.blender.org/D15297)
- Still needs feedback adjustments. See comments.

Undefined deadline

- [⚓ T96225 PBVH image texture painting implementation](https://developer.blender.org/T96225)
- Any update from Jeroen?

### To Do's

Joe:
- [ ] Auto-masking features as high priority
- [ ] Remaining high Prio bugs
- [ ] Afterwards: Brush Refactor Design
- [ ] Joe will also write an overview of the featurs being worked on in sculpt-dev

### New Tasks

None

### Other Topics

- Breaking backwards compatibility with brush refactor might not be as dire
- This means the brush refactor has less pressure on it

- Input curves for brushes
- Would you want to mix more than one?
- In some cases maybe yes, argues Joe
- For texture nodes it could give a lot of control and customisation
- For regular brush properties we'd need to define use cases
- On these use cases we can base the feature on
- Popup could save us space in the UI
- Julian and Julien discussed extending the magin to close pupups to improve usability with pen devices

- https://developer.blender.org/T98070
- Talk with Dalai on raodmap for features in upcomign releases and where this fits
- Small patch next to brush managment work?

- brush auto-masking and mode auto-masking are confusing in the UI
- With the brush amnagment project we can hide away the brush options more and make them seem more advanced
- Meanwhile the mode auto-masking optiosn can be exposed way more obviously in the header as the go-to options

- Daniel suggested to move away the meeting day from away from Wednesday
- Joe would be ok with Thrusday
- Will check with rest of module members to pick a better day.

- Node editor for brushes?
- Public discussion for node editor brush design
- The use cases and problem definitions are still not clear
- We need to research and survey what node brushes could be used for meshes
- Brush nodes were originally envisioned as a different way of customising them. Not about giving more lower level, per vertex control over them
- Texture nodes on the other hand would work per-vertex
- brush command settings stack is also still a design that can be explored
- Concerns were raised about the importance of this feature. So goals need to be clearly defined and aligned with users needs.