VRay - new sampling workflow

[NicoC]

Hello,

I'm trying to polish our workflow, now that VRay's behavior has changed quite a lot (and in an amazing direction) during the last months. In a previous thread, I was asking for details about the double Noise Threshold, but now, I'd like to know about Adaptive Amount and Min Samples. In a nutshell, is there any reason left to tweak them now (with Use Local Subdivs OFF), or should we focus on playing with Noise Threshold and MSR ? pretty obviously, I don't talk about AA Min & Max Subdivs

Thanks a lot in advance for any information about that !

Cheers.

[vlado]

but now, I'd like to know about Adaptive Amount and Min Samples. In a nutshell, is there any reason left to tweak them now (with Use Local Subdivs OFF)

Nope, there's no reason to touch them at all.

Best regards,
Vlado

[NicoC]

Thanks Vlado.
Does that mean these settings will disappear in the future ?

Regards.

[vlado]

Does that mean these settings will disappear in the future?

I would like them to

Best regards,
Vlado

[Art48]

There's people crying for less buttons - then there's people crying for even more buttons. Vlado can't do it right . Either way people will cry. Personally I belong to the "more buttons"-party. More control is always better. This would of course being an expert mode setting then and hidden in the other modes.

[vlado]

Either way people will cry.

Sometimes they do have valid points I try to get the balance right.

Best regards,
Vlado

[Alan Iglesias]

Sometimes they do have valid points I try to get the balance right.

Best regards,
Vlado

When we faced this situation in the development of Max's Interface Gary simply decided just to make everything as customizable as possible! Everyone had what they wanted, didn't have what they didn't want, and the complaining went down significantly, almost to nothing.

-Alan

[Nicinus]

One day we will look back at this era and compare it to adjusting and tweaking the carburetor while out driving so we can get to the store faster.

[squintnic]

often its the stupider arch vis people asking for these things.
the amount of people that fixate on settings rather than improving their images / animations / skills is huge.

im all for a simpler interface and love the current direction

[NicoC]

Hello,

I don't think things are as simple as "more buttons is better", or "the simplest is the better". In my opinion, flexibility often means complexity, while simplicity often implies rigidity ... the art of development is the ability to get a good balance between both IMO. On top of that, our tools like 3dsmax and VRay are used in such a wide spectrum of activities (archviz, VFX, packaging, retail design ...) that getting this balance perfect for everyone is obviously impossible. So getting things simple at first, with the possibility to access more options ("Expert" mode) seems a good path. More specifically, kicking all the subdivs stuff out of VRay (and all the trial/errors before setting final rendering settings) should make everyone happy, thus allowing us to focus on fun and rewarding stuff !

My 2 cents :P

[theedge]

For me, removing all those parameters that are no more or very rarely changed from the main V-Ray interface is fine and preferable.
As long as they remain accessible through maxscript that should be fine I think.

[thablanch]

We are getting lots of reuse projects with long term clients, where we need to get the identical result for a 'slight variation' of their product, and the image was done 4 years ago.
Whenever a button is not there anymore, well this becomes a pain for us.

Accessing it by Scripting is nice, but the office over here (and lots of places) is composed of artist, not scripters..

I do understand things need to evolve, but in my opinion, the way that the sky was treated is the best, keep the 'legacy'.
I'll have a whole lot of work in the future weeks with the Adaptive Subdivision getting out of the UI, And thanks for brigning back the Vray exposure in the environment.

[Nicinus]

I think the way Corona hides all the gooey tech parameters in a performance tab seems to work, that way I know never to go there.