Announcement
Collapse
No announcement yet.
Blender 2.82's NVIDIA OptiX Support Is Performing Very Well
Collapse
X
-
Originally posted by nokipaike View Postyou are losing the fact that rtx denoising in blender is being developed by an nvidia developer ....
or maybe it's better to say a developer sponsored by nvidia.
😉
Leave a comment:
-
Cycles with OpenCL last year has been greatly improved especially the compilation phase of the kernels before rendering.
This development was sponsored by AMD.
On the development of Optix there is now a developer who is supported by NVIDIA I'm not sure if he is directly an developer of NVIDIA.Last edited by nokipaike; 06 March 2020, 04:27 AM.
Leave a comment:
-
Originally posted by tildearrow View Post
#NoItDoesNotBecauseOpenCLStillIsSlowerThanCUDAAndI fItActuallyDidItWouldSupportHIPProRenderOrSomeOthe rAMDOnlyTech
I can see 4 NVIDIA fanboys out there.
Leave a comment:
-
Originally posted by Dunexus View Post
#BlenderJustTriesToPerformTheBestOnEachPlatformUsi ngAvailableTechnologiesAndFrameworksAndDoesItVeryW ell
I can see 4 NVIDIA fanboys out there.
Leave a comment:
-
AMD has its own rendering engine that is already optimized for Blender and available through all major OSes, this might be the reason why AMD sucks on Blender, and this is surely a huge blame!
Leave a comment:
-
Originally posted by Imout0 View Post
No, it doesn't. The initial 2.81 build slowed AMD GPUs by a whopping 50% and was partially fixed because people complained. Developers said they wouldn't waste their time fixing that any further.
It is honestly discouraging seeing how the Blender development team doesn't have the patience with OpenCL that we have with their constant fuck ups.
In 2.80, Blender devs added to Cycles the 4D nodes (noise, vornoi, etc) from the 2019 GSOC. It was always a known issue that adding these nodes would take a hit on AMD OpenCL's performance. (You can't really blame neither AMD nor blender devs for that. Blame the OpenCL spec for it). For now the problem is workarounded, but is stated that BF is working with AMD on a better solution, if any.
OpenCL is nice to use for parallelizable operations, but has quite a lot of limitations that CUDA doesn't have. You can blame Apple for these. That's why it took years (and some AMD employees) to have OpenCL support in Cycles, and that's why other render engines that support openCL have problems too (vray as example) and some others just refuse to support openCL (octane)
- Likes 1
Leave a comment:
-
Originally posted by mlau View Post
At least nvidia's tools/libs work. No one is stopping AMD from making Blender run better with their GPUs. At this point it's fairly obvious that AMD needs to invest a
lot more in the software side of things to make their hardware more appealing. Intel and ARM understand this (with their timely contributions to toolchain infrastructure, ...),
MIPS didn't (or couldn't) and they're more or less dead now.
I know people want things working but the Blender Foundation should understand that they are at this point because users stuck with them even at bad times. Throwing AMD users under the bus isn't the right way to do things and the Blender Foundation should be all about it.
Leave a comment:
-
Originally posted by Imout0 View Post
No, it doesn't. The initial 2.81 build slowed AMD GPUs by a whopping 50% and was partially fixed because people complained. Developers said they wouldn't waste their time fixing that any further.
It is honestly discouraging seeing how the Blender development team doesn't have the patience with OpenCL that we have with their constant fuck ups.
lot more in the software side of things to make their hardware more appealing. Intel and ARM understand this (with their timely contributions to toolchain infrastructure, ...),
MIPS didn't (or couldn't) and they're more or less dead now.
Leave a comment:
Leave a comment: