dforce and new NVIDA driver 397.64
Trigger_31
Posts: 19
Don't know if this is the right place here but with the new NVIDIA driver 397.64 dforce DAZ Studio 4.10.0.123 no longer recognizes a compatible CUDA card: "A valid OPenCL 1.2 device could not be found". The installed CUDA is 9.2.81. Previous drivers had the 9.1 driver. I have a GTX 1060 with 6gb vram.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I'm on 397.31 and had some issues after installing it (mainly it 'knokced by 1050 which drives my display out) and after a fair bit of messing about involving rverting, rebooting and re-installing (which did it again) the cad finally decided to start working all by itself. It also now seems to get 'jittery' when I use my other card for renddering, almost as if it is also being used, which ity shoudln't be). Knowing that the next update which I saw just after I installed this version may have dForce issues has stopped me installing it, so thank you for the haeds up!
397.31 has an issue where if your PC is idle for a period of time (not sure how long exactly), the drivers stop responding. I noticed because when I would come back from work and try to launch DAZ, I would get the error regarding OpenGL 1.3 being required. A reboot would fix the problem. I updated my drivers before I saw this, however I just went in and did a test and my 1070 showed up as a valid dForce device with the new drivers.
I'm having this same issue. It also isn't limited to D|S, so it's not a DAZ problem. Has anyone found a solution? I'm used to ME having "senior moments" and forgetting things, but to have my computer constantly (about a 24 hour cycle) forget the driver is crazy-making. I've been reinstalling the drivers, not a reboot (and the reinstall only buys me 24 hours).
The Windows 10 April Creators Update was overwriting the NVidia drivers, but the current release (and previous hotfix) should have taken care of that.
I think some of you are confusing problems here. The dforce problem is clearly CUDA / OpenCL related. Maybe some of you confuse OpenCl and OpenGL. Wiki is your friend in this case.
They're both part of the NVidia drivers; if Windows is overwriting them, both will be affected.
Sorry to have thrown the proverbial wrench into the mix here. To clarify, I was saying that the 397.64 Nvidia drivers were not giving me a problem with OpenCL and I can do dForce. But I was also noting that I had been having problems with the earlier drivers disappearing if the computer sat idle for some time, which would cause DS to fail at launch due to the missing OpenGL drivers.
So I guess I sort of hijacked the thread. Apologies.
I had an issue with Octane in Carrara that may have been the new driver update, it stopped at about 3K frames of a 7K image series, windows gave memory warnings but plenty RAM and VRAM left.
but will not know until I can restart and resume my animation, am running my weekly backup so need to wait.
what was odd it happily rendered for 4hours before this happened.
Yes, just suffered this on Win 7, bloody annoying!
I strongly suspect that it's not a driver problem but DAZ Studio needs to be updated to recognize CUDA 9.2 drivers.
I don't think so - for example I just started up Octane standalone to check and that can no longer recognise any CUDA evices, which suggets that the driver has well and truly gone for an early bath
I may have yo update driver (to a version that will, reportedly, not do dForce) so I can actually start Daz Studio without having to reboot first! Or I can wait for yet another version to come out and hope that fixes stuff. The option ro rollback the driver has now gone, so I can't even do that now (but that, at least, is not down to nVidia)!
Works fine on windows 10 april update for me had to do a complete uninstall and reinstall. The previous driver had problems with the 1060 not being recognized. Now that there will be two different types of 1060 legacy models using the GP106 GPU and newer ones using cut down GP104's
Okay,I checked with GPU-Z and it says GP106. Anyway, I reverted to Driver 391.35 and dforce recognized the card again.
no issues with Daz Studio Public build on Driver 197.64 running on windows Build 17666 Prerelease. the only time I have issues is when the cloth explodes due to a bad cloth settting I have to close Daz and reopen it to clear its kernel cache.
I'm running the Windows 10 April Update, which may be another factor as it seems that someone else running it is also not seeing this issue.
Yeah, the latest driver has issues recognizing my second Titan Xp. 391.35 is the last driver that recognizes it.
Got sick to death of any of CUDA, openCL, or OpenGL going to sleep so updated to 397.64 and I am happy to say the dForce seems to be working. Of course this coudl eb just becuase teh OpenCL support has yet to timeout on me ..
397.64 is installed and i have the problem one more time.