run through of my working method for vray 2.4 sampling in arch vis scenes.

[joconnell]

Hi folks,

I just recorded a wee video of how I approach cleaning up a vray render in a predictable way. Its a very nasty scene with the bad scenario of a smallish window for the light to get in through so it requires some fairly high sampling to clean up. It doesn't cover how sampling works in this video as Toni, akin and grant have all done good write ups of those, it's more so a start to finish walkthrough of a fairly common arch vis type interior. The HD version is encoding now and will replace the SD version so you'll get a much clearer idea of the noise I was seeing in the passes. Also note that this is done in 2.4 and there's some bits in 3 that would help even more. It's not meant to be a fully finished scene either, it's just a representation of a fairly nasty arch vis scenario.



Cheers!

http://vimeo.com/85982809

[cheerioboy]

Thanks John, epic video

I'm still going through it, but it's refreshing to see other people's processes. I think your video quite clearly shows my own woes dealing with render times & interior scenes.

[rivoli]

will have to properly watch it, as I barely had to time to skip through now, but it's already extremely fascinating to see how very good artists like you work. great effort and thanks a bunch for taking the time and sharing.

[glorybound]

can you share your script for applying subdivs per blurry values?

[m_hinks]

Very nice John, just downloading to watch with excitement. I wonder, will you update soon with Vray 3?

Mark

[glorybound]

I enjoyed the video. I like that your thinking isn't so binary. Sometimes people take things literately, and from other recent discussions might have thought brute force is the only way we should be working, which isn't totally accurate. But, having said that, have you tried brute force?

[glorybound]

Also, you mentioned using a render farm. With the image, which had a pretty low resolution, what were your PC specs? Some might say that 3 1/2 hours is huge for a small, low resolution image, and horrific on a render farm. Personally, I would be totally happy with the quality and render time, but I have heard images like that should take minutes and not hours.

[vlado]

Also, you mentioned using a render farm. With the image, which had a pretty low resolution, what were your PC specs? Some might say that 3 1/2 hours is huge for a small, low resolution image, and horrific on a render farm.

I was going to say that; 17h for the original image at this resolution seems a bit high, no matter what settings.

Best regards,
Vlado

[joconnell]

It's nasty alright - Vlado would it be worth sending the file across for profiling?

Also - worth noting that one of the last things I did was sort some intersection on the geometry (which took down our time by about 20%), since the scene is largely glossy refractions and raytracing, a large portion of that 17 hours was probably dealing with co-planer faces so it should have been a large portion less.

[vlado]

It's nasty alright - Vlado would it be worth sending the file across for profiling?

Yes, definitely. I was rendering a similar scene today and it took no more than 1h for perfect results.

Best regards,
Vlado

[Dariusz Makowski (Dadal)]

Can you upload the files scene so others can have a go at it too maybe?

[RockinAkin]

Awesome work on the video John! Thanks for taking the time to put this together!

[glorybound]

with the script you mentioned

[Neilg]

17 hours for that is madness. Count me in as one who'd love to have a go.

Solid process though - just much bigger numbers involved than i'm used to

[joconnell]

Yes, definitely. I was rendering a similar scene today and it took no more than 1h for perfect results.

Best regards,
Vlado

I'll pop you a scene to your chaos email, of course now I'm crapping myself incase I left anything embarrassingly stupid turned on