Hmmm, read all the way through this one. Been sort of interested but with DAZ Studio’s render gains in the past couple of releases and it’s ability to access all cores during the render then comparing that to using Octane, which are you saying for the free version, cuts you down to just using 2 cores to render??
The standalone 3Delight Free version available for download restricts the computer running it to 2 cores and searches for other versions of 3Delight running on the network. If it finds another, it will shut down.
The version that ships with D|S is not core locked, but does have the network abilities removed.
EDIT: The full 3Delight runs on D|S and Maya and Softimage. The cost for an additional dual core license is $400, with an unlimited core license selling for $1250.00. The yearly support cost starts at $190/yr.
EDIT2: The cost to upgrade from the Free Dual-Core to a Quad-core license is $250.
In all cases except for the Free, a license server must be running somewhere on the network and reachable by 3Delight.
ive been meaning to do some test renders but been busy rendering with other renderers tonight. Thanks for the info, I didn’t know there was an upgrade price.
Stand-alone 3Delight pricing is professional-render-house-only pricing. It’s out of the realm for hobiests. Dual core machines are ancient, and even quad cores are only mid-level machines now at best. I use Lux with network rendering, and the only quad core is my laptop. All the slaves I use are desktops in the office with 8-12 i7 cores (=16-24 threading contexts with hyperthreading, and Lux scales very well with hyperthreading). To use 3Delight with the same machines would probably cost ten grand and give worse results. (For me, anyway. There are some real masters that make 3Delight look very realistic, but it takes a lot of work. Lux is much easier to construct scenes for, in my opinion.)
Stand-alone 3Delight pricing is professional-render-house-only pricing. It’s out of the realm for hobiests. Dual core machines are ancient, and even quad cores are only mid-level machines now at best. I use Lux with network rendering, and the only quad core is my laptop. All the slaves I use are desktops in the office with 8-12 i7 cores (=16-24 threading contexts with hyperthreading, and Lux scales very well with hyperthreading). To use 3Delight with the same machines would probably cost ten grand and give worse results. (For me, anyway. There are some real masters that make 3Delight look very realistic, but it takes a lot of work. Lux is much easier to construct scenes for, in my opinion.)
But as it stands right now, Lux is significantly more limited than 3Delight. That’s to be expected though, Lux is still maturing while Renderman is in its prime.
Limited how? It’s got a pretty comprehensive set of shader types available. Usually when I see people complain about Lux, it’s because they’re trying to do things that a physically unbiased renderer can’t do, since it’s not how an unbiased renderer works. (E.g., processing a render into separate diffuse, specular, etc., passes for merging in post.)
Limited how? It’s got a pretty comprehensive set of shader types available. Usually when I see people complain about Lux, it’s because they’re trying to do things that a physically unbiased renderer can’t do, since it’s not how an unbiased renderer works. (E.g., processing a render into separate diffuse, specular, etc., passes for merging in post.)
BINGO. There are many applications where one would need to render non-physical (non-nature) light. This would include pretty much all movies as there is significantly more light in a movie scene than exists in nature. Which is why 3Delight has been used in all of the Harry Potter and X-Men movies.
Unbiased rendering, for the time being, is not useful in production.
Stand-alone 3Delight pricing is professional-render-house-only pricing. It’s out of the realm for hobiests. Dual core machines are ancient, and even quad cores are only mid-level machines now at best. I use Lux with network rendering, and the only quad core is my laptop. All the slaves I use are desktops in the office with 8-12 i7 cores (=16-24 threading contexts with hyperthreading, and Lux scales very well with hyperthreading). To use 3Delight with the same machines would probably cost ten grand and give worse results. (For me, anyway. There are some real masters that make 3Delight look very realistic, but it takes a lot of work. Lux is much easier to construct scenes for, in my opinion.)
agreed for the most part Its not necessary for a hobbits workflow but when you need to render something without crashing because your running out of RAM with Studio open it’s a very viable option,
In that case, it would be cheaper to add more RAM given the current price for RAM than it would be to purchase the stand-alone 3Delight licenses. And the extra RAM would give more overall utility.
In that case, it would be cheaper to add more RAM given the current price for RAM than it would be to purchase the stand-alone 3Delight licenses. And the extra RAM would give more overall utility.
Now, usually I’m a big fan of more RAM….but depending on the machine ‘cheap’ is a relative term. For DDR3 RAM that could be true.
DDR2 RAM has seen and will continue to see a significant increase in price. And a dual or quad core DDR2 motherboard/CPU is more than capable of running Studio and the stand alone 3Delight.
Lets use my current machine for an example. It’s a DDR2 dual core machine at 4 GB. If I wanted to double the memory it would cost me $150 to do so. But, with a free 3Delight stand alone license, I’m not losing any ‘cores’, but am gaining speed/available memory to use for the render. I can close down everything else, log out so I’m not even running X and render from the console (command line for all you Windows folks) and have very close to my full 4 gigs available for the render.
You can’t get much cheaper than a free render engine running on a free OS…yes, for those that don’t know, I run on Linux, Slackware being my preferred distro.
I just rendered this ...top image: S4.5 at about 4 mins ; bottom image: stand alone 3Delight about 2 mins (that included generating the RIB) for the standalone I didn’t close or stop anything. it rendered in the background while everything else was still running and got done about half the time of the Studio render.
I just rendered this ...top image: S4.5 at about 4 mins ; bottom image: stand alone 3Delight about 2 mins (that included generating the RIB) for the standalone I didn’t close or stop anything. it rendered in the background while everything else was still running and got done about half the time of the Studio render.
It saved that much time? Wow. I know what I’m doing next.
Basically, most of the time in the standalone render was the dump to the RIB. It took about 30 to 45 seconds to actually render it. 32.34 seconds to be exact…
And now I can run that RIB any time I want and get the render done that quick.
I think part of the time used in Studio is that every time you render, it goes through and generates new shadowmaps, runs tdlmake on the textures and so on…(not 100% about tdlmake, but I am on the shadowmaps). It probably generates fresh point clouds if using them, too.
I just noticed one odd thing…the shadows in the stand alone render seem to be a bit ‘softer’...now I’m not sure if that is because of jpg compression on the Studio render or if it is something ‘real’. My first guess is compression .
EDIT to add:
Thinking about it a bit more, Studio treats every render as something ‘new’, where as, if you’ve got a rib and all the files needed, the stand alone uses them instead of caching them. That refreshing of the cache takes both memory and time. The standalone will read them from the hard drive, while Studio has to generate them, dump them to a temp folder and then read/use them.
Holy Friggen CRAP!!! I just tried it for myself.
You could knock me over with a feather right now.
It renders raytraced transparent hair like its nothing!!!
You could set up a computer with just the 3Delight stand alone on it, on your network and dump the RIBs from Studio to it…and then run them on that machine, freeing up the machine with Studio on it. (But the same can be said for using any external renderer.)
Wow. I know what I’m doing next.