Yes but they are not global. That’s why we need to create scripts to do that. I mean if I have a scene with 200 light and 78 material, I can’t change them one by one or if I work on someone else’s scene I don’t want to have to go into each light and material to see how they are set. With a single place for all the global multipliers we see at once how the scene is set or at least we have a better global idea.
And Akin is right about the counterintuitiveness of a setting that doesn’t do anything to the end result when changed. I think that if everyone could just see what’s happening to the 4 sampling values with the feedback boxes Akin put in its interface images (min max image sample and min max dmc sample), VRay would be more intuitive.
This particular problem can be solved in other ways, f.e. by providing a tool to give you all these settings listed in one place, and potentially giving you the ability to mass-edit those settings, similar to the light lister.
With a single place for all the global multipliers we see at once how the scene is set or at least we have a better global idea.No, you just have yet one more place to have to check.
Best regards,
Vlado
Yes I understand. I think you are right on both points. And a tool like this would be awesome.
Maybe something like the Akin calculator could also be in a tool just to better see what happen under the hood.
John Martini has been working with me to script a tool to do exactly that.
It will grab all the subdiv values throughout your entire scene, list them one place, and show you the resulting min/max samples that will be taken (using the formulas from my DMC calculator) in the context of your scene’s setting.
Hopefully it’ll be ready for testing soon.
Ok wow! That’s great. If you need testers don’t hesitate to communicate with me. I was considering trying to script something myself but I’m not a master scripter.
Noone said 3d stuff is easy. Although getting more user-friendly should always be the goal.
You don’t NEED to do it!!! Use progressive rendering, leave it for as long as needed and you are done. If we removed all subdivs values from V-Ray (and I must say that I’m very very tempted to so this), this whole problem would not exist… It still mystifies me why people want to make their lives so complicated… they don’t care about how many samples any other render engine makes, it beats me why it is such big deal here.
Best regards,
Vlado
I don’t understand Recon442 either, we are not talking about doing math. But just about a way to understand how vray balances the sampling between geometry silhouette, motion blur, dof on one side and GI, shadow, ref and refrac glossiness and SSS on the other side while using 2 tools: primary ray samples and secondary ray samples. the math is thankfully done by the software, all we do is turning the knobs to make adjsutements.
Then why some people use Arnold or Maxwell and don’t care about the number of samples? It’s because they work on multi hundreds millions budget full feature films and their deadline is in 4 or 5 years and they have access to thousands nodes render farms. Or maybe just working on personal projects without any deadlines…
But when we work on more limited budgets and tighter deadlines we need to render as fast as possible with limited amount of render nodes. That’s when we need VRay and we need to know exactly where the machine time is used for and for exactly how long depending on which sampler is doing what. And that’s when we need such tools as the one we are talking about here.
Yep they work on huge budget films with pretty big render farms but they also get massive render times - a friend is using arnold and vray for commercials and he hasn’t been able to render an ad at 1080p in arnold, only 720p which is okay for our local market. In larger studios I’ve heard of 100 hour per frame render times so even if you have 100 nodes for a 100 frame shot, you’re still going to be waiting 4 days to see the results.
People that use arnold and maxwell don’t complain about the samples as they have no choice - they have no control to make their render times faster so they just accept it and move on, as a result if you want to use either render in cg heavy productions, you’ve gotta pay for the render power to support it.
It’s always the nagging though that things could be made faster and faster given a set of magic numbers I think, like if we happened upon a perfect situation that we’d be able to get full 3d motion blur and dof, per pixel gi and lots of glossy everything at 5 minutes a frame for a hd interior ![]()
With the other engines you just resign yourself to the fact that it’ll be slow and move on with your life. With vray it’s very possible to get very quick results with a lot of expensive rendering effects, it just takes a bit of effort to get it!
Hehe, and to think that I added that option for you specifically
Would make me think twice before trying something like that again.
But non the less, one really needs to have some sort of feel for the sampling balance, and some skill of prediction to be successful with Vray. At least if optimal rendertimes and quality are desired.That’s true; but as you pointed out, getting the hang of it is not that hard and comes with a bit of practice. At least you have the option to reduce render times when you need to.
Best regards,
Vlado
No, it’s not. There is still some adaptivity based on the intensity of materials and lights that remains.
Best regards,
Vlado
It can’t be like that because even if you uncheck the checkbox, there are still 2 samplers and they still have to divide the job between each other. The shading subdiv division only rebalance the secondsary rays automatically when you increase the primary rays subdivs, if you stop rebalancing automatically you will have to do it manually most of the times but that doesn’t mean the render time will increase when you increase the subdiv. Cause the render time can go lower if you use the right sampler to do the right job. So if you tell the sec rays sampler to work more by letting him send more samples it can unload the primary ray sampler and decrease render time.
And yes Vlado, that one remains a bit mysterious for me. That’s what is called importance sampling. But is that importance sampling completely automatic or is there any input value that can have a direct influence on it?
It is controlled by the “adaptive amount” parameter. If you set it to 0.0, then V-Ray will not do any adaptivity at all for secondary rays.
Best regards,
Vlado
LOL! That was exactly what I was suspecting! So now I understand another big point! Thanks!
Can you tell us what is the exact math the adaptative amount is doing to the importance sampling?
And do the primary rays also do importance sampling? (I could test this with some DOF)
And I just reread the doc: "Amount - controls the extent to which the number of samples depends on the importance of a blurry value. It also controls the minimum number of samples that will be taken. A value of 1.0 means full adaptation; a value of 0.0 means no adaptation. "
Now I understand the meaning of “importance of the blurry value”. You were talking about “importance sampling”. I should reread the doc over and and over again! i will not read them the same way now that I know everything explained by Akin and cie. I really forgot about that one. And importance is not only brightness but also distance etc.
I’m glad this is being discussed, I’ve been using Vray for about 7 years and although I love it I get tired of all the constant changing and balancing of settings that goes on. I’ve always wondered why these things aren’t automated and why there setup as they are, how changing one setting can have such a dramatic impact on render times while others seem to do nothing. It seem like the engine is overly complicated on purpose and people take a lot of pride in the fact that they’ve mastered all of it’s quirks. I know a lot of people would like to simplify things, one of reasons Corona’s getting so much attention right now is because it’s pretty easy to operate and I really want to see Vray embrace this. Just my 2 cents.
Because then people complain that they don’t have control… besides, there is no easy way to automate that. Adaptive sampling generally means that the render engine tries to guess how to get to the result faster, so by its very definition it involves guesswork to some extent.
and why there setup as they are, how changing one setting can have such a dramatic impact on render times while others seem to do nothing. It seem like the engine is overly complicated on purpose and people take a lot of pride in the fact that they’ve mastered all of it’s quirks. I know a lot of people would like to simplify things, one of reasons Corona’s getting so much attention right now is because it’s pretty easy to operate and I really want to see Vray embrace this. Just my 2 cents.You CAN run V-Ray in this mode - use progressive render mode and you’ll be fine. Like I’ve said many times before, IT IS NOT NEEDED TO PLAY WITH THE SETTINGS to such extreme confusion. Every time I’ve gotten a slow to render scene, going back to the default settings made things a lot faster and cleaner.
But, if people prefer to spend their time tinkering with settings, what am I supposed to do? Well, the obvious answer is, remove the settings
V-Ray will still work just fine and don’t think that I haven’t considered it seriously… The only thing that is stopping me is that sometimes every minute you shave off of a render is really important and it is possible in that case, to find settings that render the scene faster than the default. But, just because V-Ray gives you options to get faster renders, doesn’t mean it makes sense to use them always.
Best regards,
Vlado