Sassy Materials | Automatic PBR material network setup and texture assignment 1.0.0 for Maya (maya script)
Automatic preset shading network setup with options for searching for files according to predefined naming conventions. Comes with presets for Redshift, Arnold, and the standard lambert shader, but documentation is included on how to define your own presets for your preferred rendering engine!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Hey, that'd be possible, but very difficult. If I find time I'll try and implement an option for it, but also, I don't see this kind of texture being used a lot in production, so the tool wasn't made with that in mind. That'd also require support for adding ambient occlusion, since that's what the O channel is for.
If it's gonna be added, it would be added as a "roughness is ORM" toggle or something, and I'd have to add an optional branch for the base color that'd multiply the ambient occlusion map with it, which would really complicate things.
I appreciate your input, my summer break is coming up so I'll stew on this a little bit. I understand it's a bit of an Unreal Engine thing to use, right?
I thought ORM support would be much easier to implement because it is simply a matter of plugging individual RGB channels instead of direct connections.
reading the docs for arnold, it appears that the "base" float attribute on the surface shader is just a multiplier, so it wouldn't matter if I still kept it universal there and used a multiply before that. The reason why i prefer using a multiply for AO, is because i can still add other nodes in between to make it not look as "black", sometimes I remap or tint my AO maps a bit to make them a little more interesting.
As far as ORM goes, I want to make a V2 of this plugin when I have the time, so I'll update you when I added ORM support. I will have to shuffle some things around to improve the workflow and also update the UI a bit.
Adding support for ORM maps and other requested features would require adding a lot of catches etc, for specific workflows, so I should rethink how I am gonna do this, especially now that I've played around with USD a lil bit.
Thank you for showing interest and for your support, I'll take a look at it when I have time again.
Anyway, ORM textures may not super used in VFX production, but they are certainly used in videogames or real time applications. Substance Painter can export them easily and they are very helpfull in a glTF / USDz pipeline, since you reduce drawcalls a lot.
By the way, AO may be multiplied, but in the case of an Arnold material, it won't, it would just be plugged into the "base" component of the material (NOT baseColor), so it will be certainly be multiplied in the end by the baseColor, but both are plugged into different slots.
joie
Replies to this question:
Sasbom said over 2 years ago:
If I find time I'll try and implement an option for it, but also, I don't see this kind of texture being used a lot in production,
so the tool wasn't made with that in mind.
That'd also require support for adding ambient occlusion, since that's what the O channel is for.
If it's gonna be added, it would be added as a "roughness is ORM" toggle or something,
and I'd have to add an optional branch for the base color that'd multiply the ambient occlusion map with it,
which would really complicate things.
I appreciate your input, my summer break is coming up so I'll stew on this a little bit.
I understand it's a bit of an Unreal Engine thing to use, right?
Thanks for using my script and leaving a comment,
Sas
joie said over 2 years ago:
Sasbom said over 2 years ago:
so it wouldn't matter if I still kept it universal there and used a multiply before that.
The reason why i prefer using a multiply for AO, is because i can still add other nodes in between to make it not look as "black", sometimes I remap or tint my AO maps a bit to make them a little more interesting.
As far as ORM goes, I want to make a V2 of this plugin when I have the time, so I'll update you when I added ORM support. I will have to shuffle some things around to improve the workflow and also update the UI a bit.
Adding support for ORM maps and other requested features would require adding a lot of catches etc, for specific
workflows, so I should rethink how I am gonna do this, especially now that I've played around with USD a lil bit.
Sas
joie said over 2 years ago: