Originally posted by Bobby Bob
View Post
Announcement
Collapse
No announcement yet.
Blender's "Cycles X" Showing Nice Performance But Dropping OpenCL Support
Collapse
X
-
- Likes 5
-
Originally posted by Daktyl198 View Post
While most of your post rings true, the latest announcement from the Blender devs is only one drop in the bucket of years of posts and comments from the Blender developers. They only own NVidia GPUs, they've only ever owned NVidia GPUs, and they only code Blender and it's renderers for NVidia GPUs. IDK about "fanboy" as a correct term, but "uninterested in the other companies entirely" is a good way to describe it. Almost all of the work to support anything non-NVidia has come from outside sources. Yes, Blender is Open Source, but it's no wonder the alternatives to the CUDA kernel are so poor when the developers who know the insides of Blender the best refuse to bother themselves to spend a day on them.
Quote from the LuxCore dev on Cycle X:
Originally posted by Dade (LuxCore)Today, Blender Foundation has announced Cycle X: https://code.blender.org/2021/04/cycles-x
Aside form the consideration that we were quite right given the list of new features added and old removed: they are introducing a micro-kernel architecture (check, done many years ago), they are dropping tile rendering (check, tile rendering has always been a second grade citizen in LuxCore), volumes stack (check, done many years ago), etc.
They are also dropping OpenCL support.
On one side this is an opportunity for us because we are left as the only OpenCL option available (may be, Indigo Render is still using it too ). On other side, I consider this the official announce of OpenCL death.
R.I.P.
- Likes 2
Comment
-
Originally posted by Bobby Bob View PostFolks here calling Blender devs 'CUDA Fanboys' is hilarious.
It would have helped OpenCL years ago. Sure. Now it is totally too late. OpenCL is dead. Now everything is back to start. Cycles devs are still "CUDA fuck yeah" and everyone else has to clean up their mess again.
The only good thing now in comparison to the state years ago is that Blender now has a real-time renderer Eevee that is enough for most settings. So you don't need Cycles in Blender to get good results.
- Likes 3
Comment
-
Originally posted by tildearrow View PostNot a good idea to start on CUDA... Contradicting for an open-source project to support closed-source vendor-locked standard.
Should have started with Vulkan instead....
OpenCL has been terrible for quite some time so this is hardly surprising, its not surprising they are using CUDA since its really a question of having something of decent quality working vs a piece of crap. Its unfortunate that AMD at the time didn't have the RND or budget to work on it properly (unlike NVidia).
Maybe they can start afresh with OneAPI.
Originally posted by Daktyl198 View Post
While most of your post rings true, the latest announcement from the Blender devs is only one drop in the bucket of years of posts and comments from the Blender developers. They only own NVidia GPUs, they've only ever owned NVidia GPUs, and they only code Blender and it's renderers for NVidia GPUs. IDK about "fanboy" as a correct term, but "uninterested in the other companies entirely" is a good way to describe it. Almost all of the work to support anything non-NVidia has come from outside sources. Yes, Blender is Open Source, but it's no wonder the alternatives to the CUDA kernel are so poor when the developers who know the insides of Blender the best refuse to bother themselves to spend a day on them.Last edited by mdedetrich; 24 April 2021, 04:22 AM.
- Likes 1
Comment
-
Originally posted by Bobby Bob View PostFolks here calling Blender devs 'CUDA Fanboys' is hilarious.
If others want to try and hack in support for other APIs after the fact then no one is against that, but it's an afterthought at best for the main devs.
This is not particularly unique to the Blender devs. It's something you see over and over again in a lot of places, because the whole industry has now standardized around CUDA support. OpenCL just wasn't viable for a long time, and CUDA is pretty embedded nowadays.Last edited by smitty3268; 24 April 2021, 05:08 AM.
- Likes 2
Comment
-
Originally posted by StillStuckOnSI View Post
OneAPI level zero is arguably cleaner than the CUDA C API and has the advantage of working with standard toolchains (as does OneAPI SYCL). The main reason AMD made HIP is to ease migration for CUDA users. I highly doubt they'd design something like it if they weren't trying for that.
It's more of verbose than clean.
Comment
-
At least we don't get a code 43 on nvidia cards anymore... So at least we got that.
On a more 'clean your own room' note, AMD could have done better on support. Their project is open source. Just another day of the same after nuking their German software division.
AMD goes for the throat with their cpus. They need to replicate that same zeal on the enterprise compute side, or they are going to be left selling crypto miners and gud enuf but no DLSS/RT gpus to gamer rebels.
They should be using this time, where nobody can even buy a gpu, to bolster their software side. But, we know that ain't gonna happen.
- Likes 1
Comment
-
Originally posted by mdedetrich View Post
Vulkan and CUDA/OpenCL solve different problems (although understandably there is overlap). Stuff like CUDA/OneAPI/OpenCL is more for compute on GPU (i.e. being able to run generic code on GPU's) where as Vulkan/DirectX/OpenGL are API's designed specifically for rendering.
Vulkan is mostly rendering-oriented, but has a compute API as well.
- Likes 5
Comment
-
Originally posted by ThoreauHD View Post
AMD goes for the throat with their cpus. They need to replicate that same zeal on the enterprise compute side, or they are going to be left selling crypto miners and gud enuf but no DLSS/RT gpus to gamer rebels.
They should be using this time, where nobody can even buy a gpu, to bolster their software side. But, we know that ain't gonna happen.
Comment
-
If they had problems maintaining OpenCL, I think this is right decision, although one hard to swallow for a lot of people.
Thing is OpenCL has little future if their current backend is buggy. There is already big gap in performance to CUDA in Blender, and even if they bridged it, there is no way to leverage something like Optix/Vulkan Raytracing inside OpenCL, and so far new versions of OpenCL like 3.0 brings little hope for it. I hope vulkan/vulkan compute backend will be comming as it is only thing potentially able to compete with CUDA/Optix. OneAPI I don't think provides any advantages over Vulkan, while Vulkan probably will be able to squize everything possible from GPUs and leverage raytracing hardware as well (heck even Video hardware encoding will be in future there).
Vulkan also could be used for viewport which also could be great to use same tech for mutliple things.
Comment
Comment