Dforce not working with NVDIA Studio Driver Version: 522.30 Studio 4.21
fbell
Posts: 6
I upgraded Nvidia studio driver to latest version - NVIDIA Studio Driver - WHQL - Driver Version: 522.30 - Release Date: Tue Oct 18, 2022 and Dforce simulation reported "Unknown Iray error" preventing simulation. (DAZ Studio 4.21 / RTX 3080 notebook)
Downgraded back to NVIDIA Studio Driver - WHQL - Driver Version: 517.40 - Release Date: Tue Sep 20, 2022 and simulation worked again.
Just FYI if someone falls on same issue.
Comments
I was asking the same thing on other thread. Thank you very much for testing. I'll stick to the 517.40 driver.
Thanks for the heads up.
Thank goodness rollback is easy, because I had just installed it 2 minutes before I saw this.
Thanks for the heads up. I was wondering what the issue was this morning. Switching drivers now.
Update! It worked! Yay!
Yeah. It did not work with 522.25 game drivers either.
Nvidia are aware of this. hopefully they will have a fix "soon"
FWIW I have the same combo; 4.21+NVidia Studio 522.30 but I have a TitanXP and everything is working fine: No problems with dForce (in fact it seems more stable and somewhat faster, but I can't really state that for certain). Rendering is mostly working fine and is, in fact, more robust with GPU OOM (still not perfect - I have to restart Studio half the time). I've been able to do a number of renders at SubD 5 which, before, was pretty much beyond the 12GByte GPU RAM of the card.
When I was downloading 522.30 via the NVIDIA (GeForce Experience App) I saw that there was a beta driver, which was a higher version number than 522.30
But after I downloaded the new driver, I can't seem to find that beta version anywhere. I'm wondering if that beta version would work with Dforce?
I'm on Daz Studio 4.21 as well, Ryzen 7 5800x + 3070ti. Installed the latest Studio and Game drivers 522.x and I get the same Dforce simulation error as well. Rolled back to 517.48 Game Driver and its working again.
In fact I don't. It looks like the GeForce experience installation did not complete; the app was reporting 522.30 but the Studio logs show I have been using 417.40 (i.e. the September release). I don't think I'm going to "upgrade"...
Desktop 3080 and gaming 522 driver. Same issue.
I rolled back too, but when I did that V9 did load without her morphs, very strange indeed.
So back to the newest Driver and will wait for them to fix it.
Check This Tutorial about Resolving This issue
https://youtu.be/DGSZ-Z5rl88
Thanks!
I thought I read somewhere that the dForce problem was only happening with the Game Ready Drivers but I installed the Studio Drivers and still got the error. I reverted to the 517 driver and dForce works. I'm not buying V9 so I should be ok (I think).
The Studio drivers have been updated since this first surfaced, but the bug in OpenCL was not fixed so now it affects the current version of both Studio and Gameready drivers. nVidia is aware of and working on the issue.
I found out that uninstalling and installing the "DForce Companion Add on" also resolves the problem.
Simulation via Companion and also standard simulation worked again.
But..after 2 or 3 days I had to un,- and re-install it again because it stopped workin again^^
Is this working for anyone yet? 10/25 so it has been almost a week and still does not work for me. Using RTX3090. I tried to roll back, but the option to roll back is greyed out in device manager. Very strange.
Update. Was able to roll back to 517.40 and d-force is working. While I was fiddling around with d-force and this driver update, my render times also decreased after rolling back. I have no idea how or why.
Before update, my scene with (5) gen 8.1, 3840x2160 , pixel radius .50, samples 10,000, sub-d 2 or 3 on characters took about 47 minutes. After the driver update, it took about 1 hour 20 minutes. I thought the increase was due to something else. Now I just tested it again, and it was back down to 47 minutes. I don't know if it had anything to do with the driver, but I am happy to see the speed drop back to where it was. Thank you to the O.P. for the heads up!
laughs in iGPU
I don't think this is the nividia driver. I was having problems even previewing and the second I deleted all dforce items from the scene, everything worked fine. This is a Daz issue for 4.2
There has never been DS 4.2 and if there had been, it would have been released 10 years ago.
It is a regression in the nVidia drives affecting OpenCL, which is used by dForce. nVidia is working on the issue.
Thx for info. :)
I hope a public service announcement is made when this issue is fixed. I certainly won't be updating my nVidia drivers until I hear otherwise. DForce has become essential in today's simulations and renders. Cheers!
Driver version 526.47, issue still not fixed.
By the way, I just upgraded to a 4090 card, dforce did not work. Going back to 517.40 is not possible because it doesn't support 4090. So I don't think a 4090 card and dforce is possible right now
Hi Richard, thanks. I had filed the issue with nVidia, but the response from their support, for what it is worth, does not make me confident they are aware of or working on the issue. Of course very possible that the frontline support people don't know, but I would have expected thatthey can see the DB of bugs they are aware of and or working on. But the issue seemed entirely unknown to them.
It is listed in their notes, so the develper side is certainly aware of it.
The "open issues" are listed in the Game Ready Driver thread on Nvidia GeForce forums, rather than the Studio Driver thread.
From https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/503224/geforce-grd-52647-feedback-thread-released-102722
nVidia support had me try a newer driver today, game ready 526.61, but it still exhibits the problem.