Loading...
> >

dForce freezes

brynnamorganbrynnamorgan Posts: 6
in Daz Studio Discussion

I finally decided to try dForce and am having issues with it. At first it would simply make Daz Studio just close. I uninstalled through DIM and reinstalled manually. That got it to start simulation stabilization, but it stops at 53%, then eventually I get the "not responding" error and wind up closing it. I've even given it overnight, same thing. I switched to an earlier version of DS - 4.12 which was much more stable and still running into this issue. I've read forum threads, watched tutorials, etc. I've stripped down the scene to a G8F character and a dForce dress for testing purposes and it still freezes at 53%. Yes, I tried updating my Nvidia drivers and they were out of date, but the update made no difference.

I haven't seen this issue in a forum thread and am wondering if anyone has any ideas where to look. I'm also a computer tech, and this one has me stymied.

My setup is a Dell XPS, 32 GB RAM, 4.2 ghz Intel i7 gen processor, NVIDIA GeForce GTX 1060 6GB, a lot of hard drives (mostly external), and connected via HDMI to my big screen tv. Aside from dForce, DS chirps smoothly along without one hiccup.

Any suggestions?

 

 

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,810

    Have you tried clicking the Defaults button in the Simualtion Settings pane - Editor or Advanced tabs? What dForce items are you trying to use?

  • dijituldijitul Posts: 146
    edited January 2021

    My experience with lock ups in dforce is due to problematic meshes.  Are you simulating an existing dforce mesh product, or are you trying to create/enable your own dforce on a non-dforce mesh?  The "lock ups" usually occur when the solver gets into a problematic area.  For example, the animation is moving too fast relative to the collisions.  More information about your simulation and settings would useful.  How many frames in the animation?  At what frame rate?  Is the object a purchased product or one you made?  Is it quad or triangle polys?  Is it a thin or thick mesh?  What is the distance between the mesh and the model, and what is the collision offset set to?  Is smoothing enabled?  What level of solving are you set to (best, better?) etc. etc.

     

    Post edited by dijitul on
  • brynnamorganbrynnamorgan Posts: 6

    It's a thin mesh, quad, right up against Genesis 8 Female. It's a dress I purchased designed for dForce. I have everything on default settings. I have tried with various articles of clothing on both Genesis 8 male and female. All were purchased and designed for dForce.

    Attached are some screenshots. I used an entirely different dForce dress and Victoria 8, then a fairly normal pose. It didn't even make it to 53% this time. Crashed at 0%. I selected just the dress portion to simulate. The screenshots have the settings.

    Hope the screenshots help. :)

     

    simsettings1.jpg
    1278 x 1609 - 170K
    simsettings2.jpg
    1321 x 1596 - 181K
    dforcesettings1.jpg
    1001 x 1476 - 105K
    dforcesettings3.jpg
    808 x 1448 - 92K
    dforcesettings2.jpg
    2727 x 1526 - 698K
    dforcesetting43.jpg
    2388 x 1744 - 258K
  • dijituldijitul Posts: 146
    edited January 2021

    Thank you for the screenshots.  Some question which still remain unanswered are:  Is this an animation?  In other words, are you starting from one pose and moving to another?  If so, how many frames are in the animation?  I see you have "Start Bones from Memorized Pose" turned on.  This means it likely is going from one pose to another and if the number of frames isn't high enough, the pose may move too fast for the simulation to keep up.  Perhaps you can try increasing the Stabilization Time and/or reducing the FPS multiplier.  Alternatively, set up an animation with at least enough frames to simulate close to real-world speeds or slower.  That's all I have to suggest for now.

    Post edited by dijitul on
  • brynnamorganbrynnamorgan Posts: 6

    Nope, not an animation. In fact, I tried without a memorized pose and got the same results - a freeze. I'll try some of the things you suggested anyway.

  • PitmaticPitmatic Posts: 898

    I have had DForce lock up on me and I have found it sometimes to be caused by hair either mark the hair as not visibale in simulation or just hide it and I have had shoes cause problems so maybe try that too?  worth a go.

     

  • dijituldijitul Posts: 146
    edited January 2021

    Do you have the same issues with other dforce products?  What is the result if you follow a simple dforce tutorial on YouTube with some primitives?

    Post edited by dijitul on
  • bruce_5a50d8e52bbruce_5a50d8e52b Posts: 47

    I've had the same problem. Finally this AM I tried increasing my Windows virtual memory paging. and that solved my problem. Try that as a possible solution.  My paging size was alocated at 18GB and I increased it to 25GB.  The amount you need to use will depend on your system. Rather than trying to explain the process here I sugest checking out tutorials on youtube.  Here is a quick one for windows 11 but the process is the same for windows 10.  I hope that helps.

    How To Properly Set The Windows 11 Paging File (2022) - YouTube

  • PerttiAPerttiA Posts: 10,024

    "Not responding" does not mean that the program has crashed/frozen

  • IceCrMnIceCrMn Posts: 2,129
    edited January 2022

    I would click the little "eye" button in the scene tab to hide the hair.

    If it's hidden in the scene tab;dforce won't see it during the simulation.

    It's over her shoulders and impacting the dress.

    That's a lot of collision points for dforce to calculate, so increases the likely hood of an explosion or failure.Especaily if the hair is clipping through the dress to start with.

     

    edit: make sure nothing is clipping through the dress at any point during the simulation.Like hands, fingers,etc,etc. The dress will stick to them and and other weirdness (explode, crash the PC, lock up the viewport, all kinds of good stuff).

    Post edited by IceCrMn on
  • leonardo_3285321dleonardo_3285321d Posts: 96

    I found out that sometimes it's faster to start the scene from scratch and simulate at the end, but before adding environment, etc... Dforce will start to work again. Not sure why this happens.

  • PerttiAPerttiA Posts: 10,024

    leonardo_3285321d said:

    Not sure why this happens.

    What happens? 

  • leonardo_3285321dleonardo_3285321d Posts: 96

    Dforce freeze for long time and the simulation give crazy results after many minutes / hours.

  • PerttiAPerttiA Posts: 10,024

    leonardo_3285321d said:

    Dforce freeze for long time and the simulation give crazy results after many minutes / hours.

    What do you mean by "freezing"?

    As I said, "Not responsive" is not freezing, it just means DS is too busy doing whatever it is doing to answer mom (windows), when she's calling for him.

    The time it takes to do things is dependant of how powerful a computer one has, the GPU is the most important component but the amount of RAM is a close second. Consider 32GB's of RAM a minimum.

  • leonardo_3285321dleonardo_3285321d Posts: 96

    Yes, in this context freeze = "not responsive". The simulation is not going to give good results in these cases. By recreating the scene everything works smooth (without freeze), fast and the simulation give good results

Sign In or Register to comment.