4 ms·
From my experience rendering on GPU is not worth it when you have a lot of images to generate. Generally you want budget your CPUs cores to render a bunch of im
by Dork1234 6y ago
From my experience rendering on GPU is not worth it when you have a lot of images to generate. Generally you want budget your CPUs cores to render a bunch of images at the same time instead of one (or a few) images really fast. The more threads/buckets/blocks/threads you have with V-Ray the more overhead you are paying for. If you know what you are doing you should be able to saturate your NAS speed and/or Network bandwidth.
The other thing to consider is the evermotion dataset might contain a lot of V-Ray Materials and Layers that might be CPU only. At one point Chaosgroup had a list of all the difference between CPU/GPU, but it appears they either solved all of them and/or took the page down.
- mikeroberts3000 6y agoAh, this is all good info. Thank you. And great point about Evermotion + V-Ray materials that are CPU-only. It is certainly possible that some of those materials are CPU-only. I think the Chaos Group documentation you're thinking of is here: https://docs.chaosgroup.com/display/VMAX/V-Ray+GPU+Supported+Features https://docs.chaosgroup.com/display/VMAX/V-Ray+GPU+Supported... Indeed, at least according to this documentation, some of the render elements we are relying on to generate the Hypersim dataset are unsupported on the GPU.