I can't simulate any d-force items anymore

Epic82Epic82 Posts: 126
edited October 2022 in The Commons

I’m having trouble simulating all of my d-force clothing in Daz Studio. Even if I remove everything in a scene and just simulate d-force clothing on an unposed figure, I still get a pop-up window that says “Error preparing objects to simulate” or “Error during simulation. See log for details.” I've also closed and restarted Daz, but that didn't do anything to solve the problem either. Daz even crashed a few times when I attempted to simulate a few pieces of d-force clothing. 

I recently installed a new driver for my NVIDIA GeForce 1660 Super graphics card. I’m not sure if the new driver has anything to do with this problem. But below is I think the most relevant information from the log for the scene I want to render. I’ve never had this problem with d-force before. Does anyone know how I can solve this?

I might not respond immediately to anyone's comments, since I'm posting this early in the morning before I go to bed. But I'll respond eventually. 

2022-10-14 02:03:10.296 [INFO] :: Prepare asset load (merge): /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 07 Loincloth Genesis 8 Female.duf
2022-10-14 02:03:10.296 [INFO] :: Locking viewport redraw...
2022-10-14 02:03:10.296 [INFO] :: Viewport redraw locked.
2022-10-14 02:03:10.357 [INFO] :: Native format content directories: 3
2022-10-14 02:03:10.357 [INFO] :: Poser format content directories: 3
2022-10-14 02:03:10.357 [INFO] :: Other import format content directories: 0
2022-10-14 02:03:10.357 [INFO] :: Begin asset load (merge): /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 07 Loincloth Genesis 8 Female.duf
2022-10-14 02:03:10.367 [INFO] :: Determining missing assets...
2022-10-14 02:03:10.387 [INFO] :: Setting textures...
2022-10-14 02:03:10.392 [INFO] :: Scanning for addons...
2022-10-14 02:03:10.406 [INFO] :: Creating node geometry...
2022-10-14 02:03:10.406 [INFO] :: Creating UV sets...
2022-10-14 02:03:10.406 [INFO] :: Creating materials...
2022-10-14 02:03:10.412 [INFO] :: Resolving legacy figures...
2022-10-14 02:03:10.412 [INFO] :: Preparing modifiers...
2022-10-14 02:03:10.412 [INFO] :: Creating modifiers...
2022-10-14 02:03:10.432 [INFO] :: Finalizing modifiers...
2022-10-14 02:03:10.432 [INFO] :: Finalizing simulation providers...
2022-10-14 02:03:10.432 [INFO] :: Sorting property groups...
2022-10-14 02:03:10.441 [INFO] :: Setting up follow targets...
2022-10-14 02:03:10.441 [INFO] :: Start following: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.441 [INFO] :: Following started: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.441 [INFO] :: Connect base morphs: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.441 [INFO] :: Creating morph projection map: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.456 [INFO] :: Base morphs connected: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.457 [INFO] :: Creating morph projection map: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:10.461 [INFO] :: Finished asset load (merge): 0m 0.104s - /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 07 Loincloth Genesis 8 Female.duf
2022-10-14 02:03:11.106 [INFO] :: Unlocking viewport redraw...
2022-10-14 02:03:11.106 [INFO] :: Viewport redraw unlocked.
2022-10-14 02:03:11.273 [INFO] :: Processing morph projection queue: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:11.345 [INFO] :: Loaded first morph deltas: 0m 0.2s - /data/DAZ 3D/Genesis 8/Female/Projection Morphs/xenic101/Musculature/Hip/xPBMGluteusMaximusR_proj.dsf
2022-10-14 02:03:11.349 [INFO] :: Loaded first morph deltas: 0m 0.1s - /data/DAZ 3D/Genesis 8/Female/Projection Morphs/xenic101/Musculature/Hip/xPBMGluteusMaximusL_proj.dsf
2022-10-14 02:03:11.426 [INFO] :: Morph projection queue processed: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:14.593 [INFO] :: Stop following: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:14.594 [INFO] :: Following stopped: Priya << SYdGR Loincloth Genesis 8 Female (3)
2022-10-14 02:03:16.533 [INFO] :: Prepare asset load (merge): /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 06 Bra Genesis 8 Female.duf
2022-10-14 02:03:16.533 [INFO] :: Locking viewport redraw...
2022-10-14 02:03:16.533 [INFO] :: Viewport redraw locked.
2022-10-14 02:03:16.595 [INFO] :: Native format content directories: 3
2022-10-14 02:03:16.595 [INFO] :: Poser format content directories: 3
2022-10-14 02:03:16.595 [INFO] :: Other import format content directories: 0
2022-10-14 02:03:16.595 [INFO] :: Begin asset load (merge): /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 06 Bra Genesis 8 Female.duf
2022-10-14 02:03:16.600 [INFO] :: Determining missing assets...
2022-10-14 02:03:16.629 [INFO] :: Setting textures...
2022-10-14 02:03:16.643 [INFO] :: Scanning for addons...
2022-10-14 02:03:16.649 [INFO] :: Creating node geometry...
2022-10-14 02:03:16.650 [INFO] :: Creating UV sets...
2022-10-14 02:03:16.650 [INFO] :: Creating materials...
2022-10-14 02:03:16.656 [INFO] :: Resolving legacy figures...
2022-10-14 02:03:16.656 [INFO] :: Preparing modifiers...
2022-10-14 02:03:16.656 [INFO] :: Creating modifiers...
2022-10-14 02:03:16.668 [INFO] :: Finalizing modifiers...
2022-10-14 02:03:16.668 [INFO] :: Finalizing simulation providers...
2022-10-14 02:03:16.668 [INFO] :: Sorting property groups...
2022-10-14 02:03:16.668 [INFO] :: Setting up follow targets...
2022-10-14 02:03:16.668 [INFO] :: Start following: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.668 [INFO] :: Following started: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.669 [INFO] :: Connect base morphs: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.672 [INFO] :: Creating morph projection map: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.692 [INFO] :: Base morphs connected: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.692 [INFO] :: Creating morph projection map: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:16.697 [INFO] :: Finished asset load (merge): 0m 0.101s - /People/Genesis 8 Female/Clothing/dForce Roman Clothing/SYdGR 06 Bra Genesis 8 Female.duf
2022-10-14 02:03:17.341 [INFO] :: Unlocking viewport redraw...
2022-10-14 02:03:17.341 [INFO] :: Viewport redraw unlocked.
2022-10-14 02:03:17.346 [INFO] :: Loaded morph deltas: 0m 0.4s - /data/SickleYield2017/dForceGreekAndRomanG8F/SYdGR 06 Bra Genesis 8 Female/Morphs/SickleYield2017/Base/FBMFitnessSize.dsf
2022-10-14 02:03:17.351 [INFO] :: Loaded morph deltas: 0m 0.4s - /data/SickleYield2017/dForceGreekAndRomanG8F/SYdGR 06 Bra Genesis 8 Female/Morphs/SickleYield2017/Base/FBMFitnessDetails.dsf
2022-10-14 02:03:17.355 [INFO] :: Loaded morph deltas: 0m 0.4s - /data/SickleYield2017/dForceGreekAndRomanG8F/SYdGR 06 Bra Genesis 8 Female/Morphs/SickleYield2017/Base/FBMBodybuilderSize.dsf
2022-10-14 02:03:17.359 [INFO] :: Loaded morph deltas: 0m 0.4s - /data/SickleYield2017/dForceGreekAndRomanG8F/SYdGR 06 Bra Genesis 8 Female/Morphs/SickleYield2017/Base/FBMBodybuilderDetails.dsf
2022-10-14 02:03:17.360 [INFO] :: Loaded morph deltas: 0m 0.0s - /data/SickleYield2017/dForceGreekAndRomanG8F/SYdGR 06 Bra Genesis 8 Female/Morphs/SickleYield2017/Base/Clip Fix Front Layers.dsf
2022-10-14 02:03:17.529 [INFO] :: Processing morph projection queue: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:17.586 [INFO] :: Loaded first morph deltas: 0m 0.1s - /data/DAZ 3D/Genesis 8/Female/Projection Morphs/xenic101/Musculature/Hip/xPBMGluteusMaximusR_proj.dsf
2022-10-14 02:03:17.590 [INFO] :: Loaded first morph deltas: 0m 0.1s - /data/DAZ 3D/Genesis 8/Female/Projection Morphs/xenic101/Musculature/Hip/xPBMGluteusMaximusL_proj.dsf
2022-10-14 02:03:17.651 [INFO] :: Morph projection queue processed: Priya << SydGR Bra Genesis 8 Female
2022-10-14 02:03:17.790 [INFO] :: Loaded image: SYdGR01_Bra_Diffuse01.jpg
2022-10-14 02:13:47.741 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce GTX 1660 SUPER (Device 0).

2022-10-14 02:13:48.308 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce GTX 1660 SUPER (Device 0).

2022-10-14 02:13:48.308 [WARNING] :: ..\..\..\src\dzdynamicsengine.cpp(2489): ERROR: clEnqueueMapBuffer (-36)
2022-10-14 02:13:48.488 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce GTX 1660 SUPER (Device 0).

2022-10-14 02:13:48.491 [INFO] :: Total Simulation Time: 0.75 seconds

Capture 7.PNG
969 x 878 - 429K
Post edited by Epic82 on
«1

Comments

  • LinwellyLinwelly Posts: 5,796
    edited October 2022

    I hope someone can give you a quick help here on the forum but I would advise to submit it to the help desk as well, I'm no expert but looking at the error messages it could very well be the new driver.

    Post edited by Linwelly on
  • thrstiwthrstiw Posts: 12

    Install an older Nvidia driver. Should help.

  • Epic82Epic82 Posts: 126

    thrstiw said:

    Install an older Nvidia driver. Should help.

    I've read about other users doing that. But I've never done it myself, How do you install an older driver?  

  • The way I did that yesterday was to go into the Device Manager, either via the Control Panel or by right-clicking on the Windows Start button. Find the Display Adapter in the list and expand it, then right-click on your Nvidia card and pick properties. In the "Drivers" tab of the new window, you have the option to "Roll Back Driver", this should reinstall the previous version of the driver.

    I hope this helps.

  • Epic82Epic82 Posts: 126

    Karazu82 said:

    The way I did that yesterday was to go into the Device Manager, either via the Control Panel or by right-clicking on the Windows Start button. Find the Display Adapter in the list and expand it, then right-click on your Nvidia card and pick properties. In the "Drivers" tab of the new window, you have the option to "Roll Back Driver", this should reinstall the previous version of the driver.

    I hope this helps.

    Thank Karazu82. Unfortunately, the option to roll back the driver for my computer is grayed out. I've just watched a video about this, and I found out this means there's no actual driver that I can roll back to. This is strange because I've installed multiple drivers onto this computer ever since I purchased it in November of 2020. I have no idea what to do about this. 

    Capture 8.PNG
    414 x 469 - 21K
  • FishtalesFishtales Posts: 6,043

    Go to the Nvidia website and download the latest Studio Driver not the Game driver.

  • AgitatedRiotAgitatedRiot Posts: 4,234

    Fishtales said:

    Go to the Nvidia website and download the latest Studio Driver not the Game driver.

    Do a custom install and check the box for a clean install.

  • Epic82Epic82 Posts: 126

    Thank you, everyone. Installing an NVidia studio driver helped solve the problem.  

  • jdavison67jdavison67 Posts: 587
    edited October 2022

    AgitatedRiot said:

    Fishtales said:

    Go to the Nvidia website and download the latest Studio Driver not the Game driver.

    Do a custom install and check the box for a clean install.

    I have the latest game ready Driver 

     

    522.25

     

    If I download the earlier Studio version, the installation software says they are incompatible with my system, eventhough I let the nvidia app pick the correct version for my rig. I'm running 64 bit and the software is 64bit.

     

    JD

    Nvidia_Issues_01.png
    1106 x 490 - 38K
    Nvidia_Issues_02.png
    1064 x 711 - 67K
    Nvidia_Issues_03.png
    890 x 664 - 150K
    Post edited by jdavison67 on
  • FishtalesFishtales Posts: 6,043

    Did you uninstall the Game Driver first?

  • jdavison67jdavison67 Posts: 587
    edited October 2022

    Fishtales said:

    IDid you uninstall the Game Driver first?

     

    I tried, but cannot seem to get it to uninstall...when I do it my screen goes black and it puts it back in place.

    I set it to the basic windows display driver and get the same response from the Nvidia installer.

     

    That being said, I was simulating just fine yesterday running Daz 4.20 with my current Nvidia Game ready driver 522.25.

     

    JD

    Post edited by jdavison67 on
  • AgitatedRiotAgitatedRiot Posts: 4,234
    edited October 2022

    Type in your run box. Device Manager, hit enter>display adapters>Double click Graphics card>Driver Tab> Uninstall device> Check box delete the driver software. Restart Windows. Windows will install the default driver. Then install the Nivida drivers.

    Post edited by AgitatedRiot on
  • jdavison67jdavison67 Posts: 587
    edited October 2022

    AgitatedRiot said:

    Type in your run box. Device Manager, hit enter>display adapters>Double click Graphics card>Driver Tab> Uninstall device> Check box delete the driver software. Restart Windows. Windows will install the default driver. Then install the Nivida drivers.

     

    Yeah.... my situation was a bit more involved.

    I have a Geforce GTX Titan X 12 gig video card and after the automatic GAMEREADY update the day before yesterday, DAZ simulation stopped working, yet I could not just role back my drivers.

    Uninstalling the drivers didn't seem to help because all the nvidia drivers I downloaded continued to say that no copatible hardware was found on my computer. The only driver that would load was the new driver seen in the nvidia Geforce Experience software, which is gameready 522.25

    I searched for studio drivers, but none seemed to be certified for use with my GTX Titan X.

    On top of all this it appears that there are 2 versions of the Titan X    (the Pascal version and the Maxwell version)

    I have no clue which one I have, but I do know that all the Nvidia drivers puked on installl claiming my card was not compatible.

    Soooooooo..... I did a forced manual install* of older GAMEREADY Nvidia software (version 512.15) Picked the Geforce Titan X Pascal version, because it was the only one to choose from, and even though windows said it couldn't guarantee the drivers would work. they did!

    and I have simulation back.

    UGH!

    Hopefully the next GAMEREADY update brings it back.

     

    JD

     

    *What I mean is, I used device manager and selected my card, went to properties, and selected update driver, then I selected search for software on my computer and selected "Have Disk" Then I navigated to the nvidia drivers I downloaded, navigated to the display drivers folder, bypassing the setup.exe  Windows will then display a list of graphics cards to choose from.

    Post edited by jdavison67 on
  • SevrinSevrin Posts: 6,301

    Don't install gameready drivers for Daz Studio.  Use the Studio drivers.  Always.

  • outrider42outrider42 Posts: 3,679

    thrstiw said:

    Install an older Nvidia driver. Should help.

    Isn't is nice that Nvidia allows their customers to install previous versions of their software? It is pretty consumer friendly feature.

    It sure would be nice if some other software we use did the same. It sure would, wouldn't it?

  • Yes it would IMHO. I know of a few other software providers that do as well. So precedent is set as they say.

  • Sevrin said:

    Don't install gameready drivers for Daz Studio.  Use the Studio drivers.  Always.

     

    I was able to get a studio version loaded...finally, though it is not listed as compatible with my card... Version 517.40

    Everything still seems to be working, though it seems GPU rendering is a bit slow, and the CPU is always involved, even though at much lower amounts than if CPU rendering is checked, which drives the CPU to 100%

     

    JD

  • GeffeGeffe Posts: 63

    I see a lot of people saying just roll back to an older driver. This kind of sounds like a stopgap measure. Is DAZ patching this at some point, or are we just not to meant to upgrade our drivers ever again? I haven't seen any official comment from DAZ about this.

  • Don't think it likely DAZ will patch a problem with Nvidia drivers, more likely to agitate Nvidia to fix their own problem. Regards, Richard.
  • nVidia is looking into a recent regression.

  • Karazu82 said:

    The way I did that yesterday was to go into the Device Manager, either via the Control Panel or by right-clicking on the Windows Start button. Find the Display Adapter in the list and expand it, then right-click on your Nvidia card and pick properties. In the "Drivers" tab of the new window, you have the option to "Roll Back Driver", this should reinstall the previous version of the driver.

     hope this helps.

    This actually helped me out. yeah i feel that it may be a problem with daz and not the driver as i feel thaty daz needs to update their systems.

  • memcneil70memcneil70 Posts: 3,750

    The problem started as soon as the Game Ready Driver was updated. I haven't updated my Studio Driver yet because of this and I have no issues with simulationos.

  • crazy8phil said:

    Karazu82 said:

    The way I did that yesterday was to go into the Device Manager, either via the Control Panel or by right-clicking on the Windows Start button. Find the Display Adapter in the list and expand it, then right-click on your Nvidia card and pick properties. In the "Drivers" tab of the new window, you have the option to "Roll Back Driver", this should reinstall the previous version of the driver.

     hope this helps.

    This actually helped me out. yeah i feel that it may be a problem with daz and not the driver as i feel thaty daz needs to update their systems.

    Why would you think that? In any event, nVidia is looking into a regression with the driver so it sounds as if they think it is a driver issue - which would seem likely as it started with a driver update, and is fixed by rolling back, rather than with a Daz Studio update.

  • memcneil70 said:

    The problem started as soon as the Game Ready Driver was updated. I haven't updated my Studio Driver yet because of this and I have no issues with simulationos.

    Never a good idea. Always use the studio driver, not the game-ready ones. You only can have either Studio or Game drivers, not both.  

  • memcneil70memcneil70 Posts: 3,750

    I have the Studio Driver, but my flatmate, who does not use Daz, has a Game Ready driver on his Nvidia laptop. He had the update, and then I started to see on the forums the trouble everyone was having. This past week, Nvidia sent a notification that a new Studio Driver was available for download, but there has been no word that they have fixed the problem they created, so I have not updated yet.

  • AgitatedRiotAgitatedRiot Posts: 4,234

    memcneil70 said:

    I have the Studio Driver, but my flatmate, who does not use Daz, has a Game Ready driver on his Nvidia laptop. He had the update, and then I started to see on the forums the trouble everyone was having. This past week, Nvidia sent a notification that a new Studio Driver was available for download, but there has been no word that they have fixed the problem they created, so I have not updated yet.

    No, it's not fixed as of yet; I had to reinstall an earlier driver. I did this today; I tried them. It started to simulate than error.

  • memcneil70memcneil70 Posts: 3,750

    Thanks @AgitatedRiot, that is the first clear confirmation I have had. 

    Before this I have always updated faithfully, but this threw me a curve. Thankfully I got off Game Ready Drivers years ago.

  • FishtalesFishtales Posts: 6,043

    I use the Studio Drivers and I updated to the latest which is 522.30. I tried Dforce in Daz Studio 4.15.0.30 and Studio 4.21.0.5 Beta and it had stopped working in both. I rolled the driver back to Studio Driver 517.40 and it started working again in both.

  • oddboboddbob Posts: 348

    Richard Haseltine said: nVidia is looking into a regression with the driver so it sounds as if they think it is a driver issue - which would seem likely as it started with a driver update, and is fixed by rolling back, rather than with a Daz Studio update.

    Unfortunately the driver which causes the problem dropped in the same timeframe as the DS 4.21 update. I saw both updates at the same time, updated and shut the PC down for the day. Took a while and happening across a forum post before I worked out which had caused the issue.

  • DP WESDP WES Posts: 37
    edited October 2022

    I've found Dforce is kinda broken for me too, however. To be honest it's not reliable, I mostly work in collision mode "Best", but only somtimes in "Better", it's situtational. Something has changed, If it's simple it usually works. More complex simulations and/or if it's for an animation, especially for "Best", are more likely to freeze, fail by stalling at 0%. Cancelling doesn't work, waiting doesn't work, sometimes it's not working on it. Dforce simulations are really quick on my GPU, so if it freezes or takes ages on 0% something is wrong.

    I'm using the latest version of Daz3d, the latest studio drivers (517.40), or the RTX A6000, it's in ECC mode, as I also do other work with it and honestly, it's far more stable for rendering and everything else, even if I do lose performance.

     

    Post edited by DP WES on
Sign In or Register to comment.