Isotropix Forums

standartshader - adopting the Arnold 5 shader layout

So you'd like something that's not there? Just tell us what, we'll see what we can do.

standartshader - adopting the Arnold 5 shader layout

Unread postby bjoern » Sat Aug 12, 2017 10:54 am

I love the fact that I can use Clarrise a bit in tandem with Maya and arnold. In the sense that the shaders are the same. Or have been the same.
I used extensively Alshaders and the new standard surface of Arnold 5. And I find the new shader in A5 allot better. It would be super great if Clarrise
would mimic these parameters (with essentially the same tech from Alshaders under the hood). For a few reasons.
- The Metalness parameter is very convenient and Artist friendly (my favorite part)
- Other apps like substance or mari etc... will add the A5 shader to there list. And if Clarrise is mimicking that shader, mixed pipeline (Maya+A5+Clarrise) are easier to handle :)
Posts: 82
Joined: Thu May 11, 2017 1:43 pm

Re: standartshader - adopting the Arnold 5 shader layout

Unread postby isoyann » Thu Aug 17, 2017 1:21 pm


The purpose of the metalness concept is to get a very good compromise between simplicity and power: with a very limited number of attributes, you can approximate almost all materials.

Alshader aim a different goal: because the metalness approach, while very effective in real time and animated features (with stylized look) is often a bit limited for vfx work, it was designed using a layered approach, more flexible, more complex, but still intuitive for artists.

Mixing the two in the same shader add lot of confusion and complexity.. and pollute what was a very good multipurpose uber shader. The disney approach (pbr with metalness) is very good, but to get the most of this, it is best to have it as a separate shader.. and if you want more options, go to the original alshader layered approach.

Another issue is it is not opensource anymore.. while Alshader was a good move toward standardization, it is now a black box.
User avatar
Posts: 597
Joined: Mon Jan 28, 2013 12:11 pm

Return to Feature Requests