Adding to Cart…
![](/static/images/logo/daz-logo-main.png)
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
The '.tint' is the tint component of the texture_return called noise() defined at the top of the MDL file.
I had to raise the absorption coefficient way up to get anything. There's something stranger going on.
Here is a cube I rendered from slightly high and left.
Here's the scene.
I had to the absorption coefficient at color(.4).
Yeah, strange, lokks like some king of atmosphere.. same MDL file?
Yep. No changes excpet to the value of the absorption coefficient.
Ok, it was just a wierd interaction with the background transparency. Absorption is working correctly.
That could also explain some of the odd crashes I get in Wine...and I think its somewhere else, like in the Studio exe itself, because it gives me the crash in 3DL (32 bit, can't run Iray), but almost all of them are 3DL.
Indeed it is.
On the off behavior with the BG transparency, have you tried switching the Alpha mode to transmission objects, or primary? I guess we could also try a custom LPE here. Almost everything I do is with a transparency, so I'm always looking at the variations.
So, are you able to now reliably render now on your Mac, or are you using a Windows-based machine?
I implemented the noise in MDL instead of using bricks. It doesn't work, but doesn't crash.![frown frown](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/confused_smile.png)
I'll play with it some more after dinner.
Anybody still watching and have time to try this out? It's pure MDL and still crashes DAZ (on OS X). The noise function is taken from shaders/iray/nvidia/noise_perlin_glossy.mdl, which works, but once I apply it to a volume, everything goes south.
direct link
Well, just tested, no crash here, but no effect either...
Thanks. I posted a help desk ticket. The last one didn't go through apparently. This crashes at exactly the same address as the one you tested before. Looks like I'm SOL until DAZ releases a patch.
If you do any other render like for example v6 with other shaders do you get the same result, crash? Or just scripts dropped at shader mixer...
Oh, I only get crashes when trying to combine perlin noise with volumes. I can do uniform volumes. I can do perlin noise surfaces. I can render all day long with other materials, but Iray crashes when I try to render non-uniform volumes.
What happens (crash wise) when you render this in Interactive mode instead of Photoreal?
Aside that that, just caught something in the programming docs: "Iray Photoreal only supports a scalar scattering coefficient and hence uses the luminance of that color for this." I take this to mean there's no per-pixel information that can be passed to the function. The value is stored uypon first execution and referred to for all pixels. I.e., as jag11 has noted before, it's read once and flatly applied. No texture (procedural or otherwise) can be used.
So I'm curious: are you looking for a physically-based volumetric effect, or can you "fake" the appearance of the mist or fog or cloud that you're going after?
Strange. Did I misunderstand jag11's previous post? It seemed to me he had it working. Or is the picture posted just surface noise? Either way, it shouldn't crash the renderer.
Yep, I was only showing that the only noise I've got was on the surface and the accompanied image were the settings used.
You're right, it shouldn't crash the renderer, but I have a feeling there isn't much Da zcan do about this. If it's in the renderer code, it'll need nVidia to fix it. I don;'t know if the Iray codebase is precompiled, or object code compiled with Daz's own library, or what, but I'd wager Daz is not allowed, from a licensing perspective, to dabble with the actual nVidia codebase.
From the same programming docs, it notes as a limitation of Photoreal that the scattering coefficient is a color in MDL; it then goes on to say that Photoreal only supports the luminance component of that color, as a scalar. If the luminance is immutable once set, texturing by means of this value will not work, sadly.
I asked before if you're going after a physically-based solution, or if faking a varying volume would suffice. As I noted before, the latter can be done -- to a degree -- by using a texture in the Refraction Weight node. It obviously isn't physically accurate of anything.
Well, that about does it for that. I guess if I need heterogeneous volumes I have to use LuxRender. I'll look into the texture based approach in the refraction weight, but I don't think that'll get all the effects I want (especially snow).
Tobor, I guess for fog, this isn't bad. I was looking for something procedural, but it seems that won't be an option in Iray for a while.
It will work well enough for Streets of Old London, which is really what set me on this path to begin with.
Note: For anybody that hits this thread at a later time, the info for this is attached below.
Esemwy, It was a noble effort! The effect looks pretty good, actually.
I agree, but definetly I'd go with volumes for that.
Is that Lux? At this point, I only know it's possible. I haven't actually done any work along those lines.
Iray. It looks weird 'cause I only droped some rocks, randomly placed and then I applied the fog settings and my best composition abilities.![laugh laugh](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/teeth_smile.png)
Is that Iray Uber or something else? Oh, wait, you mean you're using several volumes with odd shapes?
Just Iray Uber. There are several volumes(rocks), but you can use one or as many as you need to the desired effect. For speed on composition purposes I used http://www.daz3d.com/nature-rocks-pack-1.
It's even worse. As I've been told by the nice people over at the NVIDIA Advanced Rendering Forums, the scattering coefficient is currently only supported as grayscale, since for many SSS applications a greyscale/white scattering would be sufficient enough, as they say. And that this limitation will be changed in some future version of Iray.
They hate us. That's the only explanation.
Now I get to spend another couple of weeks doing this all over again in Lux. I spent 10 minutes this morning with Reality 4.1, but couldn't get the volume shader to apply properly. But that's a story for another thread....
I'm going to be upgrading my Reality (2.5) to 4.1. RDNA has the better price, and it's not looking like there are any upgrade deals Still, $25 is pretty cheap anyway. I haven't fired up Lux in over a year (yeah, I know I need the new version, which apparently comes with Reality this time around). It'll be like meeting an old friend again after a long time being in the Army...
I had 4.0, so the upgrade was free. I haven't used it that much, and it's been on the shelf since Iray hit the street. I have a Linux server with four GPUs that I'm setting up as a Lux render server. That should make things interesting.
Nah, I'd say, they're just not that far into the development stage They might ignore or even dislike us...![devil devil](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/devil_smile.png)
Hate is not what Yoda teaches... and we can really be happy he didn't write the handbook!![laugh laugh](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/teeth_smile.png)
![cheeky cheeky](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/tongue_smile.png)
For anyone interested in what I learned during my quest about absorption and scattering in Iray: I answered (my own! :P) question over at Nuts n Bolts.
>>Hmm, that didn't work out as intended.<<
![cheeky cheeky](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/tongue_smile.png)