Started by WAS, April 01, 2021, 01:44:06 pm
Quote from: WAS on April 02, 2021, 02:01:01 pmWeird. Blender uses my AMD GPU fine.
QuoteOpenCL rendering kernels. The combination of the limited Cycles split kernel implementation, driver bugs, and stalled OpenCL standard has made maintenance too difficult. We can only make the kinds of bigger changes we are working on now by starting from a clean slate. We are working with AMD and Intel to get the new kernels working on their GPUs, possibly using different APIs (such as CYCL, HIP, Metal, ...). This will not necessarily be ready for the first release, the implementation needs to reach a higher quality bar than what is there now. Long term, supporting all major GPU hardware vendors remains an important goal, and we think that with this new architecture we'll be able to better performance and something stability. It is just a matter of time until more GPUs are supported in Cycles X again.
Quote from: WAS on April 29, 2021, 12:15:37 pmThat sucks. They're essentially committing suicide. I won't be using Blender any more then. Half of their used GPUs are AMD, while AMD is slower alone, it literally made up half their user base, and for controlled CPU rendering and hybrid rendering AMD CPU/GPU combos were on top.
Quote from: mhall on April 30, 2021, 10:10:23 pmMy point was simply that it really sounds like OpenCL is a PITA to work with and that is likely why so many pieces of software (like this photogrammetry one you were discussing) have have gone the CUDA only route.
Quote from: WAS on May 01, 2021, 12:13:17 amWe should have API standards honestly.