Thoughts? My goal is of course to use blender to build stuff, but also render them out performantly.
Thoughts? My goal is of course to use blender to build stuff, but also render them out performantly.
Nvidia does have some caveats for linux machines in general, it is a slight pain in the ass to deal with drivers. But at least the support is there.
I think with all the cross-platform APIs maturing it's going to matter less and less, but that is me being optimistic.
AMD seems to either be more hit or miss, OR it used to be, and a lot of that is just a poor history.
Either way the GPU buying landscape is difficult for me.
And with 2.92 it's even faster and it now supports CPU+GPU rendering with Optix. Unfortunately, AMD doesn't have such good Blender support. You're stuck with OpenCL and slower rendering time. You could try using their Prorender renderer, but to be fair, it's a closed source and non-native to Blender. I'd rather stick to Cycles+Eevee. I wish one day AMD will work with Blender to better support it, as I much prefer them as a company and I like their opensource drivers. But really, Nvidia RTX cards with Blender at the moment are fantastic.
https://www.phoronix.com/scan.php?page=article&item=blender-... and Ampere is _fast_.
Blender System Preferences for CUDA, OpenCL, and OptiX all report "No compatible GPUs found for path tracing. Cycles will render on CPU." I'm using nVidia's proprietary driver and NVIDIA X Server Settings reports 240 CUDA Cores. No Joy w/ nvidia's cuda packages, either. Blender's been running well on this workstation since ~2.7x for video editing work, so further system tweaks have been low-prio. Will revisit to look at OptiX.
That means that apps using newer versions of CUDA will not work, and your hardware is also far too old to use OptiX.
Put in another way, your current GPU is slower than the one in a Nintendo Switch...
> Fermi ... (last drivers in 2018, you're on a legacy branch).
IYO, is there any value to using legacy nvidia-driver-390 over X.Org?
> apps using newer versions of CUDA will not work, and your hardware is also far too old to use OptiX.
Will look to see if apps I use avail of my CUDA cores, else I'd prefer to remove this sole proprietary driver from my old-and-busted workstation.
Thanks again for saving me time. I’ll re-de-prioritize further GPU config hacking, though if you have suggestions for a Nintendo Switch-to-FireWire 800 interface, please share.
nouveau doesn't support compute at all on those... (as in OpenCL).
Also, as far as I remember, rechecking work on Fermi didn't seem to be implemented the last time that I played with one (it is implemented for the later generation, Kepler, though)
> Will look to see if apps I use avail of my CUDA cores
If your app is compiled against CUDA 8.0 or earlier, targeting compute capability 2.1, it'll work on Fermi. That excludes any kind of modern binaries.
(the newest compiler that CUDA 8 supported was GCC 5.3...)
More recent apps can either be built with an old compiler + C++ library... or use OpenCL instead.
>> "No compatible GPUs found for path tracing. Cycles will render on CPU."
I'll research Fermi for OpenCL and Cycles Render Devices. Blender's working well, so I'll resist the urge tweak until that's no longer the case, and hope to spend more time exploring 2.92.
tl;dr: (sadly) nVidia provides (at times _significantly_) better rendering performance than AMD due to OptiX denoising, which requires less samples per frame. CUDA vs OpenCL is - as far as I know - on par performance-wise.