Skip to content

proposal: Optional Material Override Specification for VRM1 - #516

Open
miramocha wants to merge 1 commit into
vrm-c:masterfrom
miramocha:master
Open

proposal: Optional Material Override Specification for VRM1#516
miramocha wants to merge 1 commit into
vrm-c:masterfrom
miramocha:master

Conversation

@miramocha

@miramocha miramocha commented Aug 23, 2026

Copy link
Copy Markdown

I'm proposing an optional multi-engine material/shader override specs that will work similar to how VRMC_springBone_extended_collider currently works. It will replace/extend mtoon/khr material when shader is applicable and fallback to mtoon otherwise.

Current working implementation/proof of concept:
https://github.com/miramocha/Extended-VRM-Specs/blob/main/examples/mtoonxt-liltoon-override-warudo.md

In the example implementation page, there is also MToonXT specs but please ignore it for the time being when reviewing this PR as it is not in scope.

Note that on the page/repo the extension name prefix is VRMXT_ to prevent collision with current official source, and we are replacing it with VRMC_ in this proposal.

I'll be happy to discuss, walkthrough, and take any suggestion into consideration, thank you.

Optional engine material on materials[]. Same override JSON shape; open engine strings. English only.

Co-authored-by: Cursor <cursoragent@cursor.com>
@0b5vr 0b5vr moved this from To do to Next Discussion in VRM Working Group Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Next Discussion

Development

Successfully merging this pull request may close these issues.

2 participants