[Asmithey]

My first interior renderings with Maxwell Render. This was the project I actually used to learn Maxwell Render. I just finished it a couple of weeks ago. I had to squeeze in the Telluride House, a paying job.

I started from the Form-Z model that I had built back in 2006. I began the Maxwell learning process in December 2007. The plants are xrfog material. I had to use neat image as it was still grainy at 17 SL. Rendered for 300 hours on my dual quad. I used multi light.

[Stinkie7000]

Looks pretty good!

[dynaraton]

Nice Renders.
Brutal Render Time.

[jurX]

300 hours for that pic in that resolution!?...impossible!

[Asmithey]

The resolution is 1600x1200

To be accurate it took 332 hours. My machine is a dual quad but it only has a total of 14.88 Ghz. The ram usage was low, about 2.5 gigs. Since it was still some what grainy and took so long, I am wondering if maybe I had something done improperly. Something that was not optimized for performance sake.

[JTB]

... I am wondering if maybe I something being done improperly. Something that was not optimized for performance sake.

No matter what you did wrong, 300+ hours is unacceptable....
These render times are the only reason other renderers exist.... NL, you got to do something about that!

[Asmithey]

Check this out. The renderings I did for the Telluride House, that I previously posted, took way longer. I had to use a certified Maxwell Render render farm. Those images had a lot of displacement in them.

One of the images took a total of 1,977 total cpu hours and the other took a total of 1,300 cpu hours.

But on the farm, with the images running simultaneously and at low priority, I got them in 30 hours. The image size was 3600x2400.

[Tora_2097]

There must be something seriously wrong in your scene. I can't imagine the patience to wait for 300h and not wondering whether something might be wrong. And its nonsense that other rendereres exist because of that. I could setup a vray scene with a sphere on a plane that takes a year to render as well.
Using K. Busses MXCL calculator a time of 330h @ 1600*1200 px relates to a BM of a little higher than 3.
Thats ridiculously slow.
I'd expect a BM 10 or 20 times as high in such a simple scene.
Most materials appear pretty much lambert so a guess might be to check your windowglass if there is any. Are you using AGS in the windows?
I also see a few displaced surfaces. What are your precision settings? Have you checked with DP disabled? Are the spotlight emitters modeled as a plane or sphere? Use as few polygons as possible! And do not (!) cover them with real glass, use AGS if you have to. If you using instances and are not having RAM issues without it, disable instancing it will speed things up as well.
these are a few things that spring into my mind at first glance.

Keep it up,

Benjamin

[JTB]

And its nonsense that other rendereres exist because of that. I could setup a vray scene with a sphere on a plane that takes a year to render as well.

I mean that with Maxwell's quality the only reason to choose other renderers is the time needed for interiors to clear up....
Please don't be rude unless you have to...This time you don't have to....

[Tea_Bag]

What about displacement? That could slow things down!

[Asmithey]

Hi Benjamin,

Here is how I have set it up. Most of the materials are close to Lambert. I do have some reflective surfaces. For materials that have no reflective value I use a high roughness setting any where 95 to 99. I never use straight Lambert.

I am using AGS glass for all window glass and pendant light glass. I wondered about the pendant lights causing a possible problem. I should turn them off and render it.

I do have some displacement with the stone planter beds.

All emitters are circular single sided surface planes with one normal pointing down. Except the lamps. I used a low poly sphere to get a more accurate light distribution.

I'll have to check the precision of the DP map. May be higher than need to be.

I did use instancing for the barrel cacti. It was pushing 8 gigs of ram and I only have 4. When I used instancing it was pulling about 3.5 gigs of ram.

As for the patience, it was easy. I had no deadlines at the moment.

[Bubbaloo]

I'm not going to comment on the render times, except to say at that resolution on a dual quad it should take less than 12 hours to reach that s.l.

If there's any part of the renders that could use displacement, it's the stone columns. Plus the map doesn't line up at the visible corners. That's the biggest stand-out to me.

Keep posting!

[Asmithey]

I did notice that the rendering rendered much faster without the x-frog plants in the rendering. I noticed this when I was doing test renders.

[simmsimaging]

At 300 hours I'd be getting tempted to build a physical model and take a picture of it.




b

[Asmithey]

Has anyone else used x-frog models in their renderings and experienced long render times?