Loading...
> >

DAZ studio 4.12.0.86 Dforce and NVIDIA RTX 2060 (Resolved)

gurwallbzhgurwallbzh Posts: 10
edited December 2019 in Daz Studio Discussion

Hi everyone,

I've got an issue withDforce and my Nvidia RTX2060 GPU card. I installed the Nvidia driver 26.21.14.4141 and it works fine 

with Iray. But I can not see it in the Simulation advanced tab. It looks like DAZ3D does not recognize it and only show me

the cpu option. This is really annoying. Did anyone have to solve this problem ? I read few threads in the forum but nothing solved my issue.

Cheers

Post edited by gurwallbzh on

Comments

  • Richard HaseltineRichard Haseltine Posts: 107,911

    What is your driver version in xxx.xxx (e.g. 430.86)? You can get that from the nVidia Control Panel, launched from a right-click on the desktop.

  • gurwallbzhgurwallbzh Posts: 10

    it is 441.41

  • Richard HaseltineRichard Haseltine Posts: 107,911

    That is odd - I was testing my new PC a few minutes ago, I think with that driver, and was able to simulate the Daz House Cat with my 2080Ti. Which Windows version is this, and what are the rest of the specifications?

  • gurwallbzhgurwallbzh Posts: 10

    this is a windows 7 sp1 64 version, Daz studio version is 4.12.0.86

    What other specs would you like? 

    screenshot_20191207_110033.png
    473 x 426 - 32K
  • gurwallbzhgurwallbzh Posts: 10
    edited December 2019

    Here my card appears in render tab but not in simulation

    Capture-002.PNG
    415 x 699 - 17K
    Capture-001.PNG
    424 x 709 - 23K
    Post edited by gurwallbzh on
  • Richard HaseltineRichard Haseltine Posts: 107,911

    And if you click the Intel Open CL... button the pop-up menu doesn't have any other entries?

  • gurwallbzhgurwallbzh Posts: 10

    No the pop up menu only show me the cpu. There is no entry for my GPU.

  • fdsphotofdsphoto Posts: 62

    RTX 20080 Ti with 441.41 is doing the same thing.

    Initially, my redering was kicking back to CPU. DAZ support told me to update to 441.41. That seem to fix the rendering issue, but now dForce doesn't work worth a damn.

    If i revert back to 436.30, everything seems to work but I don't think it fully levearges the full potential and capabilities of the RTX 2080 Ti.

    DAZ - you need to get it together...

     

  • Richard HaseltineRichard Haseltine Posts: 107,911
    fdsphoto said:

    RTX 20080 Ti with 441.41 is doing the same thing.

    Initially, my redering was kicking back to CPU. DAZ support told me to update to 441.41. That seem to fix the rendering issue, but now dForce doesn't work worth a damn.

    If i revert back to 436.30, everything seems to work but I don't think it fully levearges the full potential and capabilities of the RTX 2080 Ti.

    DAZ - you need to get it together...

    If it's a driver issue there isn't really anything Daz can do.

  • gurwallbzhgurwallbzh Posts: 10

    I just tried the 436.30 but unfortunatly it did not solve the issue for me.

  • fdsphotofdsphoto Posts: 62
    edited December 2019
    Richard Haseltine said:
    fdsphoto said:

    RTX 20080 Ti with 441.41 is doing the same thing.

    Initially, my redering was kicking back to CPU. DAZ support told me to update to 441.41. That seem to fix the rendering issue, but now dForce doesn't work worth a damn.

    If i revert back to 436.30, everything seems to work but I don't think it fully levearges the full potential and capabilities of the RTX 2080 Ti.

    DAZ - you need to get it together...

    If it's a driver issue there isn't really anything Daz can do.

    Log File seems to say otherwise...

    2019-12-08 15:05:11.554 WARNING: ..\..\..\src\dzdynamicsengine.cpp(425): Using device: GeForce RTX 2080 Ti
    2019-12-08 15:05:11.814 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(499): ERROR: clBuildProgram (-11)

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    CPP-499 allow local bind

    https://github.com/datastax/cpp-driver/pull/411/files

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    CL_BUILD_PROGRAM_FAILURE -11 program build error for given device, Use clGetProgramBuildInfo API call to get the build log of the kernel compilation.

    http://www.techdarting.com/2014/01/opencl-errors.html

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    2019-12-08 15:05:12.242 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(351): m_isValid = false @ dzopenclkernelfactory.h, line 118 (after loading kernel members)
    2019-12-08 15:05:12.498 WARNING: ..\..\..\src\dzdynamicsengine.cpp(3500): Error initializing OpenCL!

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Error in Line 118

    Compiler error C3500 invalid ProgID 'progid'

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Post edited by fdsphoto on
  • cm152335cm152335 Posts: 421

    get NVidia "STUDIO VERSION DRIVERS" 441.28

    not "games ready drivers"

     

  • fdsphotofdsphoto Posts: 62
    edited December 2019
    cm152335 said:

    get NVidia "STUDIO VERSION DRIVERS" 441.28

    not "games ready drivers"

     

    From DAZ Support >>>>>>>

    Unfortunately, we are not authorized to access our user's computers remotely. However, we have heard from some of our users that the latest NVIDIA update, 441.41, has fixed this issue. Will you please update your drivers directly through NVIDIA's website...

    SMH...

    Gave the studio driver a try... still the same thing.

    Post edited by fdsphoto on
  • Saxa -- SDSaxa -- SD Posts: 880
    edited December 2019

    That's odd you guys are getting that.

    Have RTX2080Ti, Driver 441.41, Win7Pro x64, DS 4.12.0.86

    RTX shows fine and works fine.  Use dForce regularily without issue.

    If i had that issue, would uninstall/reinstall my Intel OpenCL runtime and see if that fixes something in back-end.

    Post edited by Saxa -- SD on
  • PadonePadone Posts: 3,998
    edited December 2019

    As for opencl there may be conflicts when more than one device is opencl capable. I mean in my experience drivers tend to overwrite each other. Luckily you can always fix them in the registry. The link below is for amd + nvidia but the principle is the same, I guess you can use it for intel too.

    Basically you retrieve the missing driver from the driverstore folder then add it to the registry.

    https://community.amd.com/message/2909519

    Post edited by Padone on
  • gurwallbzhgurwallbzh Posts: 10

    Thank you so much just adding the key (DWORD32) solved my issue:

    HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors "C:\Windows\System32\nvopencl64.dll"=dword:00000000

    Padone said:

    As for opencl there may be conflicts when more than one device is opencl capable. I mean in my experience drivers tend to overwrite each other. Luckily you can always fix them in the registry. The link below is for amd + nvidia but the principle is the same, I guess you can use it for intel too.

    Basically you retrieve the missing driver from the driverstore folder then add it to the registry.

    https://community.amd.com/message/2909519

     

  • Richard HaseltineRichard Haseltine Posts: 107,911
    sylvie1998 said:

    The simplest solution is to uninstall Intel OpenCL software. If you have it installed DAZ Studio does not see NVIDIA card for dForce at all.

    That is not my experience - I have both available in the Advanced tab of Simulation Settings and have not had issues switching between them (though I haven't done so recently).

  • capitanharlock80capitanharlock80 Posts: 36

    Just in case someone else has this problem, I had the same issue with a 1080Ti and the 441.xx drivers; upgrading to the latest 451.48 solved the problem.

Sign In or Register to comment.