Show us your 3Delight renders
This discussion has been closed.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
You're welcome :D
Just "Kettu" is fine =) You're welcome and thanks.
Blender can bake procedural materials to image maps, if I'm not mistaken. So you could use the resulting maps anywhere.
If you ever consider getting the Substance software (or most other 3D commercial apps, like Silo), you might want to get a Steam licence. They are somewhat cheaper (and depending on the country, you may even get regional pricing that makes it even more attractive).
I even have Blender as a Steam app because the Steam client will autoupdate it, which I find super convenient.
It's exactly that, the "thin film" function. The 3Delight dudes introduce it primarily for oxide film on metals, so it's a bit more complicated to get something that looks like bubbles... maybe something like this.
...it is.
http://www.daz3d.com/forums/discussion/8736/who-said-blender-was-hard/p1
wow, very nice! But now you got me hooked, there is a thin film function for 3delight? Why have i never seen that one... just so much more to learn...
I will put my horse here as well, just because I love the way it turned out, no postwork
I like that Linwelly. :)
...did you use Esha's Grassy Grounds or AOA's Grass Shader? Whichever, it looks nice and lush.
That is AOA's grass shader, thanks a lot both of you!
Thanks! Yeah there is, it's just that the DAZ devs didn't put it in the shader mixer or anywhere else in DS - there's a number of newer functions that went overlooked like that. So you need to write RSL shaders "manually" to get to use them.
It just had to be that way... np, I'm not yet ready to write my shaders.. I guess they day will come but I'm far from that.
It's a pity, I hope they will make an effort to integrate that stuff becaus I guess at some point they will be happy to still have a GC brand independent renderer...
I guess they simply don't have a dedicated developer who would be able to keep up with everything that the DNA dudes do. For instance, 3Delight 13 is coming, and then the OSL tracer will be out of beta. The OSL tracer is leaps and bounds ahead of the RSL tracer performance-wise and seems to outdo a number of competitor CPU renderers as well. But to get it to work seamlessly with DS, you need to support a new API and you need actual OSL shaders.
So I'm not counting on there ever being official support.
DAZ is a small company, and you just cannot expect Rob Whisenant to handle it all alone.
Wait before you've tried Maya. When I did, I plain said to myself that if working in VFX means using Maya, I'd rather stay a hobbyist and stick to Blender. ...aaaalthough Blender is getting bigger (because there are more and more smaller studios).
The "hard" thing comes from "no logic whatsoever" and "just how many bugs can there be" things. At least Blender is open source.
...no conversion like 3DL to, Iray, Octane, or Lux then?
I'm sorry I don't understand why you are asking about "conversion" and what you mean by it.
...materials conversion from RSL to OSL. Iray, Octane and Lux all have material conversion routines that translate Daz .duf/RSL materials into the format they use for rendering.
Ah, those. You do realise, though, that these routines do not "convert" anything but simply read the parameter values from the DS interface? And then these parameters are inserted into the calls to similar material models of those renderers, possibly with some adjustment/remapping to account for, say, different roughness curves in the spec/glossy model.
The developers use their best judgement to figure out which material model of the target renderer best corresponds to a channel named this or that way, but sometimes the matching algos fail and the result makes little sense.
Outside of actual shader authoring in shader builder/mixer, DS is not directly aware at all of the source language that the shaders are written in. Most RSL shaders for DS historically come without any source whatsoever, only the compiled versions being supplied.
If the OSL tracer wasn't using a new API for shader calls, we could reuse the Ri API that DS already has and just use compiled .oso files instead of .sdl.
...so the new API is the issue then, bugger.
Showing an image.
...that looks really good. Love the hair. It looks like....hair.
I need to get back into working with Garibaldi, just that dealing with G3F is a bit of a pain because of the change to the mapping structure.
Well, that hasn't been an issue for me yet. I still haven't been able to bring myself to using either the G2 or G3 line of figures to any great extent.
G1 is just too darn versatile for me to give up - and since I don't really care for the whole photoreal stuff and iRay that seems to be all the rage now....
...G2 for me is not an issue as it uses the same mapping structure as "Genesis Classic" (as I call it). G3 however poses and morphs a bit better (particularly expressions). Just that the workarounds I've heard of seem kind of cumbersome.
here is another on in 3delight, though this is postworked quite much ( well for me)
...reminds me of a scene from Maleficent.
Never saw that film ( not a Disney fan here) but thanks a lot.
Nice images everyone. :) I like the light rays. Is that the 'godrays' as people call them Linwelly?
It's not the godrays as you can buy them but I used a cone (primitive) with omnifreakers ubervolume shader. the difference is that the godrays often work with suface structures that can become visible at certain angles. though there is some anhancement in postwork. the original render was looking like this:
Oooo.. Even better something a person can do themselves. I like that. I can see the difference, but still a cool effect. :)
Takes its sweet time to render though ;)