Material X workflow couple of questions

   908   6   2
User Avatar
Member
951 posts
Joined: April 2008
Offline
I am trying to establish a workflow to make simple shaders but I am stuck in with some questions:

1st question:
On the old vex shading workflow it was easy to promote the parameters to the top level of the VOP node so you could easily expose just the parameters you want so you don't have to dive inside to change it, what is the easiest way to do that with Material X?
I tried to promote it to a parameter but it wont expose on the top level.

2nd Question:
I am aware of the previous way to use tags in order to make my applied textures show up in the viewport which was exhausting btw but I can not find any documentation on how to do that with Material X in Solaris, I see that AMD shaders do that automatically but I could not find a way to do that for my own custom shaders, am I missing something?

I would appreciate any tips

Thanks.
https://vimeo.com/user2163076 [vimeo.com]
User Avatar
Member
7815 posts
Joined: Sept. 2011
Offline
mzigaib
1st question:
On the old vex shading workflow it was easy to promote the parameters to the top level of the VOP node so you could easily expose just the parameters you want so you don't have to dive inside to change it, what is the easiest way to do that with Material X?
I tried to promote it to a parameter but it wont expose on the top level.

There's not any equivalent to promoting parameters that I know of. The best you can do is do a material edit which will give you a node to modify the inputs to the material.

mzigaib
2nd Question:
I am aware of the previous way to use tags in order to make my applied textures show up in the viewport which was exhausting btw but I can not find any documentation on how to do that with Material X in Solaris, I see that AMD shaders do that automatically but I could not find a way to do that for my own custom shaders, am I missing something?

They should just work, no tagging required. Even noises and other procedural patterns should work in GL and Karma--the caveat being that only the USD MaterialX builder can be used, not the Karma Material builder, which limits node choices to just native materialX nodes.
User Avatar
Member
951 posts
Joined: April 2008
Offline
Thanks for the feedback!

About the viewport texture, yes if I do in a simple object I can see it but soon I start to add more object with textures some of them does not show on the viewport in solaris as for SOP level it does show normally if I try the same textures.

Is there something that I can be missing?
https://vimeo.com/user2163076 [vimeo.com]
User Avatar
Member
951 posts
Joined: April 2008
Offline
I noticed that sometimes I have to refresh the textures and some of them start to go back.
I also notice that the ones I use a color corrector do not show in viewport, is that correct?
https://vimeo.com/user2163076 [vimeo.com]
User Avatar
Member
951 posts
Joined: April 2008
Offline
Update:

I forgot the usd_preview surface, it helps with the visualization of the textures.
https://vimeo.com/user2163076 [vimeo.com]
User Avatar
Member
7815 posts
Joined: Sept. 2011
Offline
mzigaib
I also notice that the ones I use a color corrector do not show in viewport, is that correct?

no, it should still work

mzigaib
About the viewport texture, yes if I do in a simple object I can see it but soon I start to add more object with textures some of them does not show on the viewport in solaris as for SOP level it does show normally if I try the same textures.

Sometimes there is a delay when they stream in.

Attachments:
mtlx_demo.hip (448.1 KB)
demo_torus.png (2.4 MB)

User Avatar
Member
951 posts
Joined: April 2008
Offline
Good to know!
I will test more to get used to the delay, thanks for the feedback.
https://vimeo.com/user2163076 [vimeo.com]
  • Quick Links