Has something happened to dforce in the last week?
in The Commons
Hello,
Me again with another (probably annoying) AMD query!
I know the multiple issues with using AMD GPUs in DAZ now, but up until last week I could kind of 'short-circuit'/get around the 'error initialising openCL Kernels' by selecting a different OpenCL device from the list and then back to my 9070 under the advanced tab in dforce settings. I don't understand how or why, but this was working fine as a work around until today.
I've uninstalled & reinstalled my drivers, updated Daz, re-installed dforce essestials and no joy at all. I even rolled back my drivers to two previous versions to try that out of desperation, but no dice.
Anyone have any ideas?
Thanks!

hMBAbeH.png
103 x 100 - 21K

Comments
AMD GPUs should support OpenCL fully. It should only be for rendering AMD GPUs are an issue as Iray is made specifically for NVidia (and by NVidia).
Are you saying you get an OpenCL error?
Have you considered other ways to test that your OpenCL is correctly functioning on your GPU?
Yes I'm having an OpenCL error. Its a known issue, which is very apparent upon spending all morning Googling it.
See attachment.
I'm not sure how I'd test it outside of Daz, but I've had no other apparent issues.
It is many years ago I had an AMD GPU.
If you install GPU-Z and run it does it then say that the GPU supports OpenCL?
Yes, AMD Adrenalin also says it's running OpenCL 2.0.
So it looks to be a Daz Studio issue.
Not sure what to suggest.
You could try to "buy" this https://www.daz3d.com/daz-studio-beta
And see if that makes any difference.
Or the new DS6 alpha, but there are many things that don't work in that, but you might try dForce and potentially save and then render in DS4
The issue is long-standing, AMD does not support the older OpenCL standard while Intel and nVidia do - as well as OpenCL 2, as far as I know.
Yeah, its just odd that I could still get it to work from when I first got my new AMD card ~Apr, but as of this week, its no longer having it. There's been a change somewhere.
Maybe a driver issue, though I would think the issue has existed for so long that it would be unlikely any new hardware shipped with an old enough driver.