RobynsVeil opened this issue on Oct 04, 2008 · 57 posts
RobynsVeil posted Sat, 04 October 2008 at 10:12 PM
Quote - I need to look at the V3 coding to compare but you are aware that the matmatic script generates material based on node setting encoding. And certain references to one character may not match another (i.e. material naming convention).
Yes, I am aware of that, thank you. That is precisely what I am after. Perhaps my material naming didn't follow convention, but I would assume that compile.py would have spat the dummy as soon as it encountered that, wouldn't it?
Quote - If you are interested in creating texture, matmatic may help.
I am interested in creating and managing textures and nodes programmatically.
Quote - But if you are interested in controlling texture output (regardless of model, prop, clothing) then I would highly recommend Versatile Shader System by Bagginsbill. You have direct access to node manipulation with far better results and less time. Once VSS Pro gets released, you never have to enter the material room again!
Also, maybe you can elaborate further what your intent to accomplish using matmatic. It could help isolate your problem.
Based on what you've told me, I am quite interested in having a play with VSS... I'm quite sure it will be useful. However, one of the directions I do want to take it that of face_off and that Realism Kit, and from what I've seen of Matmatic, it looks like it could fill the bill.
I will give VSS a try - I might be trying to use a Mac truck to bring home a spool of thread.
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]