Automate Texture-loading (KMS & MaterialX)

[@matttillman9110]

Just a heads up, this doesn't work with KarmaXPU (in 19.5 at least), only Karma CPU. This is because the USDUVTexture node is a VOP, which isn't supported for XPU. Thanks for the video btw! I was exactly what I'd been looking for.

[@keithkirby7376]

thanks man ive been looking for timesavers here forever with material X. moving all the kitbash 3d sets to usd/mtlx is such an undertaking. do you have an idea how to use an attribute in the component material node in the component builder to assign all of the materials at one time? based on the shop materialpath already on the model?

[@truongtrongsang666]

Thanks Mike!

[@BGMatthews]

I am still struggling to see how this workflow helps or how it could be useful for a games artist. My pipeline is photogrammetry software > zbrush > back to photogrammetry software for texturing > substance for PBR > Unreal for shading and renders. Houdini is then used for LODs. How would materialX/solaris improve my workflow?

[@animadorazo]

faa buenisimo esto esta superfacil y util

[@arleyx7090]

Is MaterialX sort of shader for displaying material in karma?

[@mayursurkutla2362]

The concept of materialX is to create a global shading network. Shaders which can be recognised by other 3D software packages as well. That's why they're not making it vex based.

[@iluvyunie]

@@mayursurkutla2362 isn't mtlx in OSL? I think I saw that somewhere

[@mayursurkutla2362]

@@iluvyunie More of a continuation I would say. OSL was developed by sony, whereas mtlX is ILM's project

[@iluvyunie]

@@mayursurkutla2362 ahh I see, thanks

[@TheMichaelBJohnson]

@@iluvyunie No, MaterialX generates shader code. OSL is one of the formats it can generate.

[@sumiderodemierda6624]

what a mess

[@Alexs_Music_Comps]

Its the future. And there is no way around anymore when it comes to usd. All future workflows are on usd. Even smart devices using usda files today. All current highend filmstudios using usd. Its not a mess its just a new workflow :-)

[@roybatty2268]

@@Alexs_Music_Comps it is still a mess. There are still UI improvements that can be made to make the process faster and less aggravating.

[@Alexs_Music_Comps]

@@roybatty2268 of course you can always improve any workflow. I can say for myself. Till Houdini 19 the workflow was quite bad and buggy. This has drasticly changed with 19. You can use it in production and in fact once you got familiar with it you will never want to go back to obj space. Of course my experience is only based on RenderMan. So i dont use multimaterial approaches

[@roybatty2268]

@@Alexs_Music_Comps Oh dont get me wrong, it is drastically improving and I as well am moving away from obj where appropriate. Just it is still not intuitive. Today I was refreshing my memory on CGwiki and the docs for Solaris / MTX / Karma / USD etc and about to get back to it right now, because it is where I need to be. Doesn't make it any less of a pain point because it is the way things are going. Best wishes, Alexander

[@Alexs_Music_Comps]

@@roybatty2268 hopefully soon Sidefx and Pixar's RenderMan will release the large Solaris Workshop that i made with over 20 Gigabytes of data. There are a lot of handy tricks inside to make the life working with it a little easier. Yes alot of things could be improved. Such as autorenaming of corresponding prim var variables across all nodes inside of a lop network. Its a pitty sometimes to rename path variables manually node by node

[@juancarlosgzrz]

What are you talking about? just hit open file and that's it

[@pizola3285]

I get the idea. The execution is not very nice.

[@zedeon6299]

Holy shit that's a lot of step just for loading texture, blender can automatically load texture with 3 button

[@grproteus]

T a l k s l o w l y

[@roybatty2268]

KZbin allows you to slow the video