To get the model into Rhino I exported the scene to the OBJ format, then imported that into Rhino. I had to fix up materials quite a bit. I made some minor corrections to the model as well (light fixtures were a bit off).
This scene I used to test my fix for multi-GPU rendering. Below you can see that I used an RTX A6000 and an RTX 5000. That is 1500 samples in 2 minutes and 8 seconds. The same scene with just the RTX A5000 would take around 3,5 minutes. This fix will be in Rhino 7.7.
Rolf, thanks, i’m lazy, I prefer a healthy disorder to a fake order!
We would have to define the whole frame (from where the light enters) … that part is only sketched … everything else seems good to me.
The composition of the scene is mine, but the credit goes to Vray. You can’t ask for better (even if it’s not the only great engine, there are many others …).
fwiw: I wanted to know what V-ray would be capable of in 1min22s, on my relatively old hardware, so I quickly threw this scene together and this I think shows that with the right software, CPU rendering is still up to its task:
The denoisers in Rhino are all post-effects outside of my rendering. You’ll have to poke @DavidEranen, @andy and @johnc about that. FWIW, running the denoiser on every pass will slow down rendering quite a bit. Right now I believe denoising, if enabled, kicks in at about 5 seconds into the rendering and then once every second.
FWIW2 I tend to turn off all post effects, since they take up processing power. Even gamma, and I would also turn off tonemapping if possible at all. That will speed up rendering also quite a bit. I enable them once the rendering is done.
exactly that. I always need many test renders before the final result, this denoising is a huge time saver to more quickly evaluate the result closer to what the render is converging to. Compared to the time per pass there is hardly any penalty.