Loading...
> >

dForce items are erroring out.

wildbillnashwildbillnash Posts: 757
in New Users

I'm finding several of my dforce hair and clothing will error out within 20 minutes when simulating.  This makes me hesitant to buy any dforce items in the future.  I'm using Daz 4.12 on my PC using a G8 figure.  One of the outfits that is erroring out is the CB School ! Outfit 2.  Here's the info listed in the log (like I really understand what it's saying).

2019-12-01 15:06:51.354 Spring(8975, 8986) of node "CB School Skirt" extended: rest length < collsion offset (0.18744 < 0.20001)
2019-12-01 15:06:51.355 Spring(312, 844) of node "CB School Tie" extended: rest length < collsion offset (0.186968 < 0.20001)
2019-12-01 15:06:51.356 Spring(388, 619) of node "CB School Tie" extended: rest length < collsion offset (0.227965 < 0.40001)
2019-12-01 15:06:51.356 Spring(389, 620) of node "CB School Tie" extended: rest length < collsion offset (0.212696 < 0.40001)
2019-12-01 15:06:51.359 Spring(533, 728) of node "CB School Tie" extended: rest length < collsion offset (0.26383 < 0.40001)
2019-12-01 15:06:51.360 Spring(534, 536) of node "CB School Tie" extended: rest length < collsion offset (0.251831 < 0.40001)
2019-12-01 15:06:51.361 Spring(535, 730) of node "CB School Tie" extended: rest length < collsion offset (0.267329 < 0.40001)
2019-12-01 15:06:51.362 Spring(536, 731) of node "CB School Tie" extended: rest length < collsion offset (0.326267 < 0.40001)
2019-12-01 15:06:51.362 Spring(537, 732) of node "CB School Tie" extended: rest length < collsion offset (0.347436 < 0.40001)
2019-12-01 15:06:51.394 Shortest spring had length: 0.0447708
2019-12-01 15:07:01.967 Loaded Morph Deltas in 0 min 0.0 sec.
2019-12-01 15:07:01.967 Loaded file: pJCMNeckFwd_35.dsf
2019-12-01 15:07:21.958 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:08:56.177 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:10:46.726 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:12:48.929 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:14:52.129 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:17:00.661 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:19:07.893 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
2019-12-01 15:19:44.512 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 960 (Device 0).

2019-12-01 15:19:44.514 WARNING: ..\..\..\src\dzdynamicsengine.cpp(2961): ERROR: Memory Object Allocation Failure (-4)
2019-12-01 15:19:44.620 Total Simulation Time: 12 minutes 57.39 seconds

Anyone have any ideas what's going on.  

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,133

    Were there a lot of

    Spring( # ) of node Item extended: rest length < collsion offset

    messages or was that it? Having a lot of those can at best slow the process and can throw the simulation out entirely, in my experience.

  • barbultbarbult Posts: 24,686

    The memory allocation failures look more concerning than the spring warnigs.

  • Richard HaseltineRichard Haseltine Posts: 102,133

    Yes, but a fair few things can - I think - cause memory errors.

  • barbultbarbult Posts: 24,686

    The simulation was progressing for 13 minutes, it seems. The memory allocation failures occurred about 13 minutes after the spring warnings. Maybe dForce simulation requires more memory as it goes along? Maybe there is a memory leak? Some GTX 960s have only 2 GB video RAM. Maybe that is not enough for a complicated dForce simulation?

  • wildbillnashwildbillnash Posts: 757

    I have no idea what you two are talking about.  My computer has 32 gigs of ram. My card is a GeForce GTX 960; but I don't remember how to check the memory for it.  Are you saying I will need a new card?

  • wildbillnashwildbillnash Posts: 757
    edited December 2019

    Had another dforce dress blow up.  Okay, I finally found the info on my card.  Here's it is...

    Geforce GTX 960

    Total Available Graphics Memory: 20449 MB

    Dedicated Video Memory:             4096 MB

    System Video Memory:                  0 MB

    Shared System Memory:               16353 MB

    Okay, what am I missing and how can I improve it.  If I need a new card (btw, my card's driver is updated) what card is best for Daz, as well as doing videos and Photoshop.  This computer is my gaming and graphic design computer.

    Any suggestion?

    Post edited by wildbillnash on
  • sildenafil@gmail.comsildenafil@gmail.com Posts: 7

    I had the same thing last night.  I upgraded my drivers (I know you said yours are) and it recompiled something the first time I simulated again and everything worked.  Maybe try a little older driver version?  That was one solution I found when looking thru Dr. Google.

    Your card is a couple years old and a x60 series so replacing it if you can afford it will certainly help speeds.  A x70 series will typically have more video memory which means larger renders can be performed with your gpu.  A 1070ti or 2070 is good, but are ~$350-500.  

  • My 3D SpinMy 3D Spin Posts: 608

    Try to simulate with Pose off in the simulation setting. That works mostly better!

  • TDBAGZTDBAGZ Posts: 165
    edited December 2019

    Cloudtask? Are you not rendering on the card?

    - Double check your simulation settings are correct.

    You have 2-4gb of vram on the card. Which is low. You want 8gb or better Id say especially if your doing Iray. Which is now set up for the RTX 20 seriesCards.

    - Try simulating in textured view if you're not already.

    - Try decreaseing the number frames you're simulating and see where it fails. 

    - Also might try simulating one item at a time. 

    Might help determine if its GPU getting juiced.  

    Post edited by TDBAGZ on
  • wildbillnashwildbillnash Posts: 757

    My 3D Spin, I didn't see a "Pose" off option but I did find a "Start Bones From Memorized Pose" option which I turned off.  It worked, mostly.  I have a leg going through the backj of the dress.

    TCBagz, a few things you mentioned I don't understand.  Cloudtask?  Not Rendering on the card?  Haven't the slightest idea what you meant.  I am simulation in textured view, that's the first thing I did.  Thanks for the tip0 on the card series.  I just don't want to go out and buy a new card and it's outdated next month.  Frames per second is set at 2, if that's what you meant by the number of frames.  And simulating one thing at a time?  How do you do that when you have a dforce hair with a dforce dress?

  • My 3D SpinMy 3D Spin Posts: 608

    If you have both hair and clothes that are D-Force- Hide one of them and render one at a time!

  • TDBAGZTDBAGZ Posts: 165
    edited December 2019
    wildbillnash said:

    My 3D Spin, I didn't see a "Pose" off option but I did find a "Start Bones From Memorized Pose" option which I turned off.  It worked, mostly.  I have a leg going through the backj of the dress.

    TCBagz, a few things you mentioned I don't understand.  Cloudtask?  Not Rendering on the card?  Haven't the slightest idea what you meant.  I am simulation in textured view, that's the first thing I did.  Thanks for the tip0 on the card series.  I just don't want to go out and buy a new card and it's outdated next month.  Frames per second is set at 2, if that's what you meant by the number of frames.  And simulating one thing at a time?  How do you do that when you have a dforce hair with a dforce dress?

    - In Simulation Settings tab Advanced make sure the OpenCL is set to render through your Graphics Card, even it says so now, click it to be sure. Cloudtask might be referencing a setting availible to some for processing sims through DAZs systems, like cloud rendering.

    - I mean the total number of frames you have set in the Timeline to process the simulation. More frames more processing memory needed.

    - Turn visibility off, or turn off simulation under Surface settings, for all dforce items except 1 at a time. You can then work from the figure out simulating each item by itself. (Dress - Simulate, Save. Tie - Simulate, Save. Hair - Simulate, Save.)

    You're basically trying to pull the load off the GPU because it's screaming Im sure. Thats not to say Dforce or even just One Dforce item isn't bugged. This may also help you determine if it is just one item with too many vertices or collisions, or if that neck bend morph is busted.    

     

    Post edited by TDBAGZ on
  • wildbillnashwildbillnash Posts: 757

    Thanks for the info, you two.  Spinner, I didn't know if hiding the one would work.  Good to know.  Bagz, thanks for breaking it down for me.  I'm going to have to play with the settings.

    I did find if I only try to simulate without an enviroment, as well as anything else in the pic, I have better luck with it.  Except when I need a floor for skirts to drape on, then I have to use a basic flat image for it.  Works great.

    Thanks again for the help.

  • middle_watchmiddle_watch Posts: 69

    I find spring warnings can usually be mitigated by reducing the Collision Offset value in the Surface Parameter menu, the value needed is usually indicated in the warnings but I just move the decimal point left until the warnings reduce to a brief burst or disappear all together.

    Freezing after 1-10 seconds after starting simulation I found on a recent garment was due to the polygon density, this is not to be confused with the SUBD value which according to the blurb has no effect on simulation, I mean the actual number of polygons used to draw the clothes. In my case I had a pair of pyjamas made in Marvelous Designer with a density set to 5, reducing density to 10 and re-importing the outfit cured the issue, but left me with awkward artefacts at the joints, so I put the density back to 5, exported top and bottom seperatly and simulated them seperatly in Daz, problem solved. I could have tried leaving them at density 10 and applying SUBD but I avoid this as it makes it difficult to judge how to tweak the results in MD while developing the outfit.

    The clue on my machine was the RAM memory maxing out in task manager, even though I have a healthy 16 GB of RAM.

Sign In or Register to comment.