D-Force. Error preparing objects to simulate?

Im getting this frequently. Anyone know what is causing this error?

«1

Comments

  • Closing out of Daz and restarting generally helps me. It's annoying if the scene takes long to load, but yeah... Also, I think the warning reads "perparing" or some other typo, which drives me nuts.

  • Closing out of Daz and restarting generally helps me. It's annoying if the scene takes long to load, but yeah... Also, I think the warning reads "perparing" or some other typo, which drives me nuts.

    I  actually tried that and kept getting the same error. It seems to have corrected now though. I found out that dforce seems to ignore items that it cant see (visibility off). By turning the visibility off of every non-collision essential item off (hair, eyelashes, etc) and turning off smoothing, it seems to have fixed the issue.

    Who knows...smiley

  • mx90209mx90209 Posts: 69
    edited March 2019

    I got this error once when I used the NVIDIA CUda Gefore CPU as the OpenCL device (under "Simulation Settings", "Advanced"), but when I switched to my Intel HD Graphics 520 card, it worked, so it can be a card-specific error as well. (restarting daz3d worked as well)

    Post edited by mx90209 on
  • frankrblowfrankrblow Posts: 2,052

    Have you tried using DS 4.11 Beta? It seems to be more robust as far as dForce is concerned, in my limited experience with it.

    I generally create scenes in 4.10, then if dForce bites the dust there, I open the scene in 4.11 Beta, and so far it's been good.

  • SwanSwan Posts: 134

    So fricking annoying...

    Happens A LOT in 4.12.

  • hansolocambohansolocambo Posts: 649
    edited August 2020

    Annoying in 4.12 indeed. As far as I'm concerned restarting DAZ / reloading the scene, has been so far enough to fix the issue. 
     

    mx90209 said:

    I got this error once when I used the NVIDIA CUda Gefore CPU as the OpenCL device (under "Simulation Settings", "Advanced"), but when I switched to my Intel HD Graphics 520 card, it worked, so it can be a card-specific error as well. (restarting daz3d worked as well)

    I use an RTX 2080 and there's no other choice than NVidia CUDA in simulation > Advanced.

    Post edited by hansolocambo on
  • I had to rebuild the full scene... reload didn't help. 

  • Try disabling the max FPS setting on your graphics card in nvidia if you have a value set there.

  • chevybabe25chevybabe25 Posts: 1,318

    Occasionally, Studio loses the dforce part of the modifier.  If It is cloth, try to reapply the dforce cloth modifier.  If it is a strand-based hair object, delete it, and add a new one to the scene. If it still doesn't work, you may need to file a ticket.

  • This issue seems to occur also in the latest version of DAZ (updated to April 2022). It is a memory issue--at least in my case--which disrrupts the simulation process midways.
    I suggest secluding the objects neccassary for the simulation and save them as a subset. Create a New scene and upload just the subset. It should work.

  • AgitatedRiotAgitatedRiot Posts: 4,582
    edited April 2022

    Jeromelevaiath said:

    This issue seems to occur also in the latest version of DAZ (updated to April 2022). It is a memory issue--at least in my case--which disrrupts the simulation process midways.
    I suggest secluding the objects neccassary for the simulation and save them as a subset. Create a New scene and upload just the subset. It should work.

    I do one Actor at a time. Pose the way you want, use the whole timeline to sim each Actor, and save each as a sub-scene. I use a plane and if it's a sitting pose I have the chair slide under the Actor towards the end of the scene. Been working well for me, so far. Just keep the same scene each time, delete the Actor set up your next Actor run the sim the whole animation time leave the start with the memorized pose on or it will set the Actor to its zero point of load.

    Post edited by AgitatedRiot on
  • welp after all the trouble shooting and a basic ball in the scene nothing works cool guess d-force is broken for me in 4.21

  • oddboboddbob Posts: 439

    Nvidia driver game ready driver 522.25 caused this on my system. Going to studio driver 517.40 fixed it.

  • memcneil70memcneil70 Posts: 5,297

    It is not Daz Studio, it is the Game Ready Driver that broke simulation. Changing your driver to the Studio driver will fix this.

  • Is there any other fix besides rerolling back nvidia drivers? I need them updated to the latest for some games I play, but I also want to simulate dforce clothing/hair in daz, how in the heck could they broke that with new drivers?? I do not understand.

  • 3DMinh3DMinh Posts: 286
    edited October 2022

    There is a new studio driver 522.30 , can someone test if the problem is fixed? Thanks.

    Nevermind the new driver still have issue with D-force.

    Thanks.

    Post edited by 3DMinh on
  • memcneil70memcneil70 Posts: 5,297

    When I booted up my laptop to download Vicky 9, I was told a new studio driver was available. After hearing the problems with dForce the Game Ready driver has, does anyone know if the Studio Driver is fixed?

  • Downgrading Nvidia drivers for RTX 3070 from  522.25 to studio or game driver 517.40 solved the problem.

  • OVDOVD Posts: 262

    siotech2011_3b5ef7af7e said:

    Downgrading Nvidia drivers for RTX 3070 from  522.25 to studio or game driver 517.40 solved the problem.

    Can confirm that it seems to be the newest driver that was causing the issue. Fixed it on a 3080 ti as well. 

  • mx90209 said:

    I got this error once when I used the NVIDIA CUda Gefore CPU as the OpenCL device (under "Simulation Settings", "Advanced"), but when I switched to my Intel HD Graphics 520 card, it worked, so it can be a card-specific error as well. (restarting daz3d worked as well)

  • I had this error yesterday after editing a dForce Modifier Weight Node Map, I stupidely did (Weight Editing /Fill) set the selected surface to 0 % instead of 100 %. 

  • kcam002kcam002 Posts: 4
    edited October 2022

    This same problem started last night for me. Updated my game ready graphics drivers to 522.25 and have even tried swapping to the studio driver 522.30 and "Error preparing objects to simulate" just keeps coming up. Even went so far as to completely reset the PC and re-install everything. The error comes up no matter which character or d-force clothing I use on it and have even tried it without any anatomy add-ons and on a scene with no environment. Nothing has worked so far. Looking to see if someone can point me in the right direction.

    Post edited by kcam002 on
  • kcam002 said:

    This same problem started last night for me. Updated my game ready graphics drivers to 522.25 and have even tried swapping to the studio driver 522.30 and "Error preparing objects to simulate" just keeps coming up. Even went so far as to completely reset the PC and re-install everything. The error comes up no matter which character or d-force clothing I use on it and have even tried it without any anatomy add-ons and on a scene with no environment. Nothing has worked so far. Looking to see if someone can point me in the right direction.

    Use an older driver

  • Ghosty12Ghosty12 Posts: 2,080

    And the latest 526.47 driver still has the same issue. So the only reliable driver for dforce is still the 517.48 version.

  • oddboboddbob Posts: 439

    Ghosty12 said:

    And the latest 526.47 driver still has the same issue. So the only reliable driver for dforce is still the 517.48 version.

    It's listed in the known issues on the driver page now though -

    [Daz Studio] Application crashes after updating to latest driver when trying to run simulation [3838022]

    So at least we'll know when they fix it.

  • Ghosty12Ghosty12 Posts: 2,080
    edited October 2022

    oddbob said:

    Ghosty12 said:

    And the latest 526.47 driver still has the same issue. So the only reliable driver for dforce is still the 517.48 version.

    It's listed in the known issues on the driver page now though -

    [Daz Studio] Application crashes after updating to latest driver when trying to run simulation [3838022]

    So at least we'll know when they fix it.

    Hopefully it is soon, as not really wanting to roll back drivers for dforce, so while we wait for a fix there is the CPU option to fall back on. smiley

    Post edited by Ghosty12 on
  • eque78eque78 Posts: 9

    My Dforce broke with the latest 522.25 driver.  Installing a clean version of 517.48 drivers via Custom Installation resolved it.

  • HaruchaiHaruchai Posts: 2,026

    New Game Ready drivers - 526.86 - released 10 November 2022. Issue not resolved.

    Just an FYI for if people are wondering when they can update to a new fixed Game Ready driver. Not yet :)

    (Also can't see any mention of this in the known issues section, unless I missed it).

  • Richard HaseltineRichard Haseltine Posts: 107,987
    edited November 2022

    The drivers with the fix are now due for release next week, Game Ready and Studio.

    Known Issues was updated to reflect this.

    Post edited by Richard Haseltine on
  • HaruchaiHaruchai Posts: 2,026

    Richard Haseltine said:

    The drivers with the fix are now due for release next week, Game Ready and Studio.

    Known Issues was updated to reflect this.

    Thank you for the update Richard, much appreciate the info. 

Sign In or Register to comment.