Indigo Renderer 3.6.15 Beta Release

[CTZn]

I created a shared param with a blank space in the name and Indigo crashed.

Thanks for reporting, looking into that now.

Fixed for the next release :)

Thanks fused !

[CTZn]

RMAN is the very special beast, notably in shading terms, and its tech is only available as an option at the best for commercial applications.

I think that the way Maya and other apps are managing 3d textures was simply meant as a more artist-friendly alternative to RMAN, allowing previz by having all the data evaluated on a lowpo.

[juan_irender]

If I want to use a dist( coords, voronoi3d( coords ) ) wich does circular gradients, to color and displace a horn say, by the time the mesh was displaced the volumetric point that will shade is left behind. Fail.

Hi CTZn.
I think Indigo is doing right in terms of displacement+shading. I´m testing your shader, and if you disable the ISL code of the albedo channel, you obtain the same result: jagged rings.
So I have located the line in your displacement shading code that produces the jaggies:

Code: Select all

def Aging() real:
	smoothstep(0.0, 1.0,fract(stretchedCylindricalFunction() * paramAge()))

¿What if we modulated the fract result with some noise?

Code: Select all

def Aging() real:
	smoothstep(0.0, 1.0,noise01(fract(stretchedCylindricalFunction() * paramAge())))

Then we obtain proper displacement (almost) that match the albedo patterns (see the pic).
So its like a problem of aliasing! Altough your code produces smooth results in the albedo and bump channels, in the displacement channel we get stepped rings. A curious effect, nonetheless, maybe Ono can explain us.

Ciao.

[CTZn]

Altough your code produces smooth results in the albedo and bump channels, in the displacement channel we get stepped rings.

Albedo is not smooth between two transitions, there's a neat colour swap happening.

Fract is meant to produce these jagged rings, hereabove exagerated by me. To me they are a key feature of wood, only that two very different colour for albedo don't fit, and it took a smoothstep for that effect to show up in bump mapping, found that out recently.

If the issue is an aliasing issue I don't understand this. Wait and see :)

edit: I must add: nice trick with noise, I did that on albedo not disp myself :facepalm:

[juan_irender]

OK, I get you.
I was thinking that the problem was the jagged look of the rings! Then the aliased look was produced intentionally.
But now, after making some more renderings I see what did you mean: the pattern produced by the albedo code doesn't match with the displace pattern (pic). We can see it very clearly at the sphere´s equator.
So there seems to be a problem with the shading of the points after its displacement, as you said...
Lets wait and see.

[CTZn]

That's far better than what I got to. I was pointing out a more radical orientation issue. Hey Juan, share some !

btw the jagging was default subdivision scheme's, I didn't bother sry.

[juan_irender]

There´s not much to say, as I´m running your shader unmodified.
Maybe object dimensions has to do: the sphere has a diameter of 2 m.
I left here the scene.

[juan_irender]

Here´s a pic with the sphere down to 20 cm of diameter.
Material looks quite right!
Maybe there´s some problems with the default material scene?

[juan_irender]

RMAN is the very special beast, notably in shading terms, and its tech is only available as an option at the best for commercial applications.

The newly released PRMAN 18 incorporates pathtracing as a new raytrace hider:
http://renderman.pixar.com/resources/cu ... acing.html
Seems that they promote its use for fast re-rendering instead for producing final images.

Ciao.