MMDShaderDev has most inputs you need, you can disconnect links, remove/add nodes inside this node group, as long as you don't remove the default inputs & output, it won't break mmd_tools. Since we don't know what result you preferred, you have to tweak nodes by yourself. You can start an empty scene -> add an simple mesh object -> add a material to the mesh object -> change alpha value of MMD Material, and start to tweak nodes of MMDShaderDev & MMDTexUV in Shader Editor, then save it as a version of your startup file. (Or else, if you've already done that- have you?- maybe that feature isn't working right?) Many mmd models use "shared toons" that are contained in the data folder of your MMD directory. If you're having problems from toons, you probably need to specify your shared toon folder. Creating models for MMD, creating/tweaking/editing animations, modifiers that allow modelling/animation effects not possible in MMD, etc. While improved materials are a good use of MMD Tools, there are plenty of other reasons to use it. Its existence means that workbench (texture view), eevee, and cycles all have reasonable shaders for editing. Removing it would do nothing to make it any easier to create a custom shader. The default Cycles conversion isn't particularly the same as the MMD shader (which is terrifically painful to implement in Cycles). If somebody wants to make their own material, there's nothing stopping them from doing that, and having an existing material with the texture node inputs is a useful start.
0 kommentar(er)
