If that would be the culprit in this scene and it would be a bug of some sorts, I wonder if that would be the same problem with the other scenes Bernard mentioned. That would mean scenes with environment fog + gizmo’s + interior should render faster or I’m missing something else?
It could be… once I disabled the environment fog and compared the results to that other renderer, there really wasn’t a big difference. There’s some stuff related to the max. ray intensity that I want to check too - I think it might be leaving some of the fireflies even though it’s supposed to clean them up, but I’m not really sure and I will need to debug it.
Best regards,
Vlado
I am thinking about the same thing too. Recently we have jumped from 3.2 to 3.4 and even though I have read every single thread / post about the new optimization (I had alot of free time =D) I couldn’t get -especially for interiors -a reasonable rendertime as what we have before when we used to optimize our scene manually.. The problem also as if vray now look at the final result only (beauty pass)?! and it is somehow clean enough but the render elements is way noiser than the old way before converting to VBAS.. I was planning to post a comparison the next week before reading this thread and I will see if I can send one of the problematic scened we had recently.
And I 'm really interested in hearing more about Bretnard scene.
Best regards,
I would like to add that I am not saying this new update is bad. for some cases like exteriors and studio product scenes the render time is great (1-3 min per frame for full HD studio lighting animation with complex materials /fur/ motion blur and dof on my 32 threads machin which is crazy good !!
There is nothing terribly wrong with Bertrand’s scene, apart from the slow environment fog. V-Ray does leave a bit more fireflies than I would like for the given max. ray intensity, and they require somewhat longer to clean up, but other than that, result is comparable to other renderers (although things can always be improved, certainly).
If you feel like you have issues, letting me know (preferably with specific examples) is the best way to go ![]()
Best regards,
Vlado
I agree that removing the fog evens the score quite a bit on the speed side. Still, the issue with fireflies means there is some hard-to-resolve noise in the scene for a long time. Leaving aside the issue of comparing V-Ray to other renderers, it feels to me as though V-Ray is super-optimized right now for exteriors or product shots--anything where direct lighting dominates over GI. Scenes where 90% of the light comes from the GI have, I believe, become harder to render as we’ve moved towards making BF/LC the standards and transitioned towards a renderer that doesn’t require users to spend hours tweaking a million settings (which I think is a good thing).
I know these scenes will always be harder to render. But if we want to keep the focus towards more simplicity, which I love, should we perhaps have a preset or setting that expedites rendering in these circumstances?
I would just rather work on making the renderer better in these cases without adding presets
As I said, we still have a few tricks that we can implement, and things are not that bad even now.
Best regards,
Vlado
No, those were off in Bertrand’s scene when I got it, though I enabled them for my own tests. Indeed they might cause some slowdowns compared to previous versions, but on the whole other speed-ups in V-Ray usually compensate for that.
Best regards,
Vlado
Very interesting thread !
are there ways to solve these problems? what’s up ?
Some problem here… with BF + LC interior renders take long times… and not always I’m able to get clean GI… it’s a little bit frustrating… sometimes even decreasing noise treshold to ridicolous values doesn’t help to clean renders… light scenario is very simple in my last project: VraySky + portals + disk lights… but renders come very noisy…
When I’m using GGX vs Blinn I notice that GGX produces a hell of a lot more noise. So for big surfaces I tend to avoid GGX.
There is a bug with light portals - they render a lot noisier than they should. This is fixed for the next SP.
Best regards,
Vlado
Really? Portals decrease noise and rendertime for me… they very useful… I did a comparison today…
Yes, but they can be better…
Best regards,
Vlado
Are you talking of 3.40.02 or 3.40.03?
Any tiny ETA on the SP? ![]()
50 bucks on “soon” ![]()
The current plan is to have a beta at the end of October, but we’ll see how it goes.
Best regards,
Vlado
BBB3,
I am curious what your final resoltuion / render times tend to be, and what is exceptable for your scenes? These vary quite a bit from user to user, and how much machine power you have.
The point I was making wasn’t so much about rendering being short or long per se but more about the fact that I had the feeling I had once be able to render similar scenes noise-free in older V-Ray versions using the approach of the time (lengthy setting optimizations by hand) than I was now with more recent versions using the recommended default settings. I also felt that some scenes today were not able to resolve noise-free in what I would call an acceptable time. This is all very subjective, of course, but in the old days, when we were all still using bucket rendering, you could roughly gauge how fast or slowly a hi-res still would render by watching the first buckets resolve. If the first buckets got stuck doing nothing for 20 minutes, you knew there was a problem with your settings. In the latest version of V-Ray, I felt (again, subjectively) that I was getting too many of these scenes where, when switching to bucket mode, the buckets stayed stuck, suggesting a very long render time for the full image.
Like I said, this is nothing scientific and it may be that I’m comparing apples and oranges since my scenes today are obviously more demanding than what I was doing on a smaller system with V-Ray 1.5.
That said, I would expect an interior still at 3K to resolve fully in something between 2 and 5 hours on a twin Xeon (32 cores).