Don’t forget we are in a different time zone 
I’ll bump it up.
It’s using the full capacity of the CUDA cores. RT cores support is coming, but not yet.
Adaptive dome is still in WIP??
Wow, IPR in 3dsmax workspace window is great !
so that demo was with a single RTX 2080?
Without trying to poke to bees nest, were any of the IPR improvements a result of the Corona merge? It looks like the IPR in Vray is now on par with Corona’s speed so I can’t help but wonder. Especially since exactly a week ago they released V3 with IPR improvements themselves
Looks like a great update! The only thing I am missing is the new Toon Material that the Maya version got. Is this coming to 3ds Max as well?
Well, judging by the change log, some improvements were made based on scenes I sent as help for the bug hunt/ as requested feature:
(*) V-Ray IPR: Improve interactive responsiveness with heavy scenes;
(*) VFB: Lens effects size to accept values lower than 1.0;
(*) V-Ray IPR: Stalling the whole UI in scenes with many VRayScannedMtls;
So, if you have any problem, report it and send a scene where the issue occurs. Yes, it takes time to prepare. But for the developers this is a really good way to analyze a problem and your bug/feature will be adressed.
I am still confused why the default IPR render time is set to a minute. That has to be the first things new users are confused about and everyone else changes each time. Just a small contribution from me
No, not really; the engines are way too different. V-Ray already had the speed, we just needed to optimize parts of the code so that updated pixels can be shown on the screen as quickly as possible, and improve the preview of the light cache to show something more meaningful. (Where “just” actually means quite a lot of work )
Best regards,
Vlado
Hm, that’s a very good observation Thanks for the pointer. Will think of ways to improve this. Maybe the default time limit generally needs to be zero.
Best regards,
Vlado
There are two final pieces that prevented us from removing the WIP label and enabling it by default. The first is implementing the consistent lighting elements for GPU (will be done in a few days with the hotfix) and the second is artifacts in the matte/shadow render element. This render element is a bit tricky to calculate in a consistent way; we have the code working but it wasn’t tested well enough to go into the official update now.
Best regards,
Vlado
Is this specific for GPU or for CPU as well?
We have the matte/shadow render element on CPU only. It can be easily simulated by dividing the lighting by the shadow render elements and inverting the result.
Best regards,
Vlado
Fantastic update
I’m using Viewport IPR and am desperate for a region render in that mode. Is that a possibility ?
I always changing this to zero too. I think Zero makes much more sense.
One question Vlado. IPR in viewport looks insteresting, but I always use VFB color settings to color correct final image. Cant find those settings in IPR viewport. Is there a way how to change this or at least use settings from VFB? Looks like viewport IPR compelety ignore them.
My guess is the Viewport IPR feature, is relying on a feature, built into Max, and IPR in the viewport, while a handy feature, would be, at least for me, ONLY for preview purposes and if you really want to use the VFB controls for colour correcting the image, then if I were you, I would use Viewport IPR. If I am wrong, then please feel free to correct me. I don’t know it al and I don’t pretend to
We are thinking about the best way to use CC in the Viewport IPR, so it will come to you at some point.
Interesting, thanks Vlado. The IPR is definitely way more responsive now, even on my 4790k at home. My main reason for switching to Corona for private work was because of the IPR responsiveness which is much needed when you’re a shading/lighting artist. Now that reason is no longer valid..
Out of curiosity, what are the changes made to the IPR to get it faster? What is the reason for the major speedup?