Loading...
> >

dForce problem

WallflowerWallflower Posts: 35
in Technical Help (nuts n bolts)

Hello.

Can someone pelase tell me how can i fix this issue ?

 

 

Thank you.

Comments

  • SimonJMSimonJM Posts: 5,999

    I think it may be a driver issue - which will require a reboot.  It happened to me (Win 7, nVidia driver 397.31) after I updated drivers.  After an unknown period of time any 'idle' component (CUDA, OpenCL, OpenGL) just 'went away' only coming back after a reboot.  Now on ltest (397.64) and despite a thread suggesting dForce does not work I am not finding an issue - yet!

  • WallflowerWallflower Posts: 35
    SimonJM said:

    I think it may be a driver issue - which will require a reboot.  It happened to me (Win 7, nVidia driver 397.31) after I updated drivers.  After an unknown period of time any 'idle' component (CUDA, OpenCL, OpenGL) just 'went away' only coming back after a reboot.  Now on ltest (397.64) and despite a thread suggesting dForce does not work I am not finding an issue - yet!

    So that means i can no longer use dForce, right ?

  • OdaaOdaa Posts: 1,548
    edited May 2018
    Wallflower said:
    SimonJM said:

    I think it may be a driver issue - which will require a reboot.  It happened to me (Win 7, nVidia driver 397.31) after I updated drivers.  After an unknown period of time any 'idle' component (CUDA, OpenCL, OpenGL) just 'went away' only coming back after a reboot.  Now on ltest (397.64) and despite a thread suggesting dForce does not work I am not finding an issue - yet!

    So that means i can no longer use dForce, right ?

    It means you need to figure out what your video card is called and download the newest drivers software for it from the video card manufacturer website :)

    Post edited by Odaa on
  • fastbike1fastbike1 Posts: 4,078
    edited May 2018

    That driver should support OpenCL.

    @Odaa > Per the screenshot it's a GTX 1080 and the driver is the one previous to the latest driver.

    @Wallflower 

    Go to the Simulation Settings Tab>Advanced and make sure your GTX1080 is selected. Sometimes Studio defaults to the onboard driver. See the attached screenshot.

    Capture.PNG
    674 x 853 - 26K
    Post edited by fastbike1 on
  • WallflowerWallflower Posts: 35
    fastbike1 said:

    That driver should support OpenCL.

    @Odaa > Per the screenshot it's a GTX 1080 and the driver is the one previous to the latest driver.

    @Wallflower 

    Go to the Simulation Settings Tab>Advanced and make sure your GTX1080 is selected. Sometimes Studio defaults to the onboard driver. See the attached screenshot.

    That's exactly where i am and there is no selectable option, only this error :

  • fastbike1fastbike1 Posts: 4,078

    Does Iray see your GTX1080? Same type tab but under Render Settings

  • SimonJMSimonJM Posts: 5,999

    A pain, but if you reboot and go straight into Daz Studio and check is the card recognised as a valid dForce device?

  • ExeterExeter Posts: 65

    I just had that happen. The latest Windows update overwrote my nVidia driver with its own. I went to the nVidia website, downloaded the latest driver for my card, installed it, and the problem went away.

  • SimonJMSimonJM Posts: 5,999
    edited May 2018

    I may be wrong but I think there are two problems .... one is the nVidia drivers Win 10 seems to want to install, screwing up OpenCL - see post above by @Exeter about that.  The other is one (or two?) recent nVidia drivers with (at least) Win 7 which 'allow' components (such as OpenCL, OpenGL, and CUDA support) to 'go dormant' and requiring a reboot to wake up - the latest (397.64) looks to have fixed this..

    Post edited by SimonJM on
  • WallflowerWallflower Posts: 35
    Exeter said:

    I just had that happen. The latest Windows update overwrote my nVidia driver with its own. I went to the nVidia website, downloaded the latest driver for my card, installed it, and the problem went away.

    Thanks for all your replies and helps. The solution above just solved my problem. 

     

    Love you, KISSSSSSSSSS. kiss

     

     

  • fastbike1fastbike1 Posts: 4,078
    edited May 2018

    @Wallflower "The solution above just solved my problem."

    Don't forget this, it won't be the last time Windows 10 does this to you. Replacing Nvidia drivers with a bad Windows Nvidia has been going on since the first release of Windows 10.

    Post edited by fastbike1 on
  • WallflowerWallflower Posts: 35
    fastbike1 said:

    @Wallflower "The solution above just solved my problem."

    Don't forget this, it won't be the last time Windows 10 does this too you. Replacing Nvidias drivers with abad Windows Nvidia has been going on since the first release of Windows 10.

    I won't, thank you.

Sign In or Register to comment.