transfer_material: transfer per-face assignments to topology-matching targets - #8
Open
hazelp343 wants to merge 2 commits into
Open
transfer_material: transfer per-face assignments to topology-matching targets#8hazelp343 wants to merge 2 commits into
hazelp343 wants to merge 2 commits into
Conversation
This was referenced Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completes the remaining item from #6 (and stacks on #7 — this branch includes those commits; happy to rebase if #7 lands first).
When the source object carries multiple materials (per-face assignment),
transfer_materialnow reads each shading engine's face-set membership on the source and re-applies it on every target whose face count matches the source's, viacmds.sets(..., edit=True, forceElement=engine)— the proper fix #6 sketched. Targets with different topology fall back to the whole-object assignment of the first material, and the status message says exactly which path each target took instead of printing an unqualified success.Single-material sources keep the simple path: one select + one
hyperShadecall, selection restored in afinally, long names throughout (all carried over from #7).I have already installed it in Maya and tested it in my scenario — per-face transfer on duplicated meshes with two materials, and the whole-object fallback on a differently-subdivided target.