Loading...
> >

Cannot perform dForce simulation: Error initializing OpenCL kernels (Windows + AMD)

therry_e35e822bb8therry_e35e822bb8 Posts: 16
edited February 2022 in Technical Help (nuts n bolts)

Hello,

I have Windows 10 and AMD Radeon 5700 XT GPU. When I try to do dForce simulation Daz Studio first says that dForce kernels need to be compiled. Then it compiles them for a while, and this always results in the error: Error initializing OpenCL kernels.

Version details:

- GPU Drivers: 22.1.2 (newest one)

- Daz Studio 4.16 Pro (newest one, although Daz Central insists that Studio version is 4.15...)

- Selected OpenCL Device in Daz Studio advanced settings is the only one available, AMD Accelerated Paraller Processing gfx1010:xnack-

- Tried with multiple scenes, e.g., with the included simple sheet drop demo scene

Any insights? Is it practically impossible to use AMD GPU with Daz Studio, or should this work? Both render engines work fine, although lray is slow (CPU only).

Post edited by therry_e35e822bb8 on

Comments

  • SpaciousSpacious Posts: 481
    edited February 2022

    DForce kernels always need to be compiled the first time you run a sim after updating drivers, so that part is normal, sort of.  Sounds like maybe your driver got corrupted somehow.  You may want to redownload and update your GPU driver.  Windows often messes with GPU drivers as part of a windows update, and occasionally even without a windows update. If that's not the problem it likely won't hurt anyway.

    Otherwise, sometimes dForce will just fail, and give that same warning "Error initializing OpenCL kernels" if there is a lot of geometry in your scene.  It's trying to load everything to use as dForce collision objects.  Fix this by hiding everything in your scene that the dForce object is not going to colide with.

    Post edited by Spacious on
  • therry_e35e822bb8therry_e35e822bb8 Posts: 16

    Well, after I first got the error I updated the GPU drivers manually to the latest ones, but that did not help. Also, there is not much geometry in the included dForce demo scene, so no help from that either. Thank you anyway for the ideas.

    Maybe I try total GPU driver removal and re-install.. although now that I have googled it seems that I am far from being alone with this problem. I wonder if anybody is using dForce succesfully with, for example, Radeon 5700 XT?

  • therry_e35e822bb8therry_e35e822bb8 Posts: 16

    Oh, some more Googling (don't know how I did not find this yesterday) and found this: https://www.daz3d.com/forums/discussion/504356/dforce-error-initializing-opencl-kernels

    No help though.. (or maybe the last link will contain something useful, must check when getting back home)

  • PerttiAPerttiA Posts: 10,024

    Do you have Intel or AMD CPU?

    Intel CPU's do have OpenCL driver, but you have to download and install it by yourself.

  • therry_e35e822bb8therry_e35e822bb8 Posts: 16

    Intel, but quite old one.. have to examine that route also.

  • therry_e35e822bb8therry_e35e822bb8 Posts: 16

    Turns out that I have this problem: https://www.daz3d.com/forums/discussion/511551/can-t-compile-dforce-kernels-get-linking-error

    So there are things like the following in Daz Studio logs:

    lld: error: undefined hidden symbol: find_coplanarity_times
    >>> referenced by C:\Users\xxxx\AppData\Local\Temp\comgr-3e3242\input\linked.bc.o:(calcVertTriCollisionCollidePoint)
    >>> referenced by C:\Users\xxxx\AppData\Local\Temp\comgr-3e3242\input\linked.bc.o:(calcVertTriCollisionCollidePoint)
    Error: Creating the executable from LLVM IRs failed.

    Maybe I still try to install Intel CPU only OpenCL implementation, but I suppose the problem is with Daz Studio, not AMD drivers as I begun to think.

  • therry_e35e822bb8therry_e35e822bb8 Posts: 16

    It seems that "Intel CPU Runtime for OpenCL Applications for Windows" works, although very slowly.

  • haplo2013haplo2013 Posts: 11
    edited February 2023

    I still have no luck with dforce on my AMD computer :(

    Post edited by haplo2013 on
  • ctkassemctkassem Posts: 0

    I'm rezzing this because I found what worked for me.  GPU=7900XTX and CPU=9800x3d.

    After trying multiple solutions including a regedit, the following steps worked, so in DAZ I now have 3 more OpenCL Device options and the "OpenCLOn12 AMD Radeon 7900 XTX" loads the kernels and dForce functions.

     

    I uninstalled "OpenCL™, OpenGL®, and Vulkan® Compatibility Pack" and used DDU to uninstall my GPU driver and Adrenaline software.

    Reboot.

    First, installed OpenCL™, OpenGL®, and Vulkan® Compatibility Pack (Run as Administrator).

    Reboot.

    Second, installed Adrenaline and GPU drivers.

    Reboot.

    Open DAZ3, change the OpenCL Device to "OpenCLOn12 AMD Radeon 7900 XTX"

    Click "Simulate."

    Microsoft OpenCL Compatability Pack:  https://apps.microsoft.com/detail/9nqpsl29bfff?hl=en-us&gl=us

    AMD Adrenaline Download:  https://www.amd.com/en/support/download/drivers.html

  • ZarconDeeGrissomZarconDeeGrissom Posts: 5,414
    edited July 7

    that Microsoft OpenCL Compatability Pack was worth a try. never had issues with OpenCL in the past before getting this 16GB RX9060XT. as of typing this, there is only 2 drivers for the thing, the review pre launch driver I can't get and the launch day one (excluding a beta driver I have no interest in till it's stable). I guess some don't work with developing software for non-nvidia GPUs that often as a few GPU compute things had issues on the new card.

    rrr, poking around, looks like the particular GFX1200 is borked, the microsoft thing added some "OpenCL on12 AMD Radeon RX9060XT" that does work, hmmm. Thanks much for the microsoft link, didn't know that was a thing.

    20250707_DforceOpenCL_error_01002.png
    394 x 168 - 8K
    Post edited by ZarconDeeGrissom on
  • acidfast22acidfast22 Posts: 6

    I am STILL having this problem with DAZ. Any help would be appreciated - even DAZ tech support can't give me an answer. I have gotten the error "Error initializing OpenCL Kernels" to clear occasionally by unistalling, rolling back, re-installing my AMD drivers but now not even that will work. I have tried MANY "solutions" (regedit suggestion, un/re-instlaling OpenCL for windows, (as stated before, rolling back, uninstalling and reinstalling drivers for AMD GPU) and nothing will work. After all the money I have paid for products from this company, its infuriatiing that I can't even simulate a simple piece of fabric on a model (with absolutely nothing else in the scene, so the "scene complexity" is a non-issue).

    I am running Windows 11 

    CPU: AMD Ryzen 7 5800X 8-Core Processor (3.80 GHz)

    GPU: AMD Radeon RX 6650 XT

  • charles-holden_d8fd00bdefcharles-holden_d8fd00bdef Posts: 1

    acidfast22 said:

    I am STILL having this problem with DAZ. Any help would be appreciated - even DAZ tech support can't give me an answer. I have gotten the error "Error initializing OpenCL Kernels" to clear occasionally by unistalling, rolling back, re-installing my AMD drivers but now not even that will work. I have tried MANY "solutions" (regedit suggestion, un/re-instlaling OpenCL for windows, (as stated before, rolling back, uninstalling and reinstalling drivers for AMD GPU) and nothing will work. After all the money I have paid for products from this company, its infuriatiing that I can't even simulate a simple piece of fabric on a model (with absolutely nothing else in the scene, so the "scene complexity" is a non-issue).

    I am running Windows 11 

    CPU: AMD Ryzen 7 5800X 8-Core Processor (3.80 GHz)

    GPU: AMD Radeon RX 6650 XT

    Hi, after MUCH trial and error, fiddling and going completely left-field, I installed the OpenCL runtime for Intel CPU. This, apparently, works on AMD CPU's as well...

    Intel® CPU Runtime for OpenCL™ Applications with SYCL* Support

    I have an entirely AMD system, similar to yours (RX 6700XT, and a Ryzen CPU), but once you've installed the runtime, go to the Advanced settings in your Simulation pane, and you'll see your CPU listed. Switch to that, and you're good to go..

    At least, it worked for me!

Sign In or Register to comment.