Dforce Doesn't Work Right

I got a new computer just when 4.11 came out. It is fantastic, renders literally takes seconds in some cases now. However, Dforce hair and clothes is giving me fits. When I clock SIMPULATE simple setups take a long time. Complicated ones will never finich. I tried letting one run overnight and it went from 51% to 58% after running 10 hours. Is this a 4.11 problem? New computer? There is a setting I am not aware of? Worked OK on the old computer with 4.10 though it was slow but slow was better than never finishing.

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,712

    What is the OpenGL Provider (Advanced tab of Simulation Settings)?

  • mwokeemwokee Posts: 1,275

    That appears to be it, the option was not set for my video card. I will have to play with it to verify. I seem to keep finding the things not covered in the online tutorials.

  • mwokeemwokee Posts: 1,275
    edited July 2019

    Still having problems. The simulation runs and completes now but I still have instances where the clothes explode into a graphical mess. The text below is from the error log after the simulation ran:

    2019-07-21 15:44:14.035 Spring(47584, 47605) of node "Granny Nightgown" extended: rest length < collsion offset (0.161013 < 0.20001)
    2019-07-21 15:44:14.035 Shortest spring had length: 0.0228234
    2019-07-21 15:52:15.807 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
    2019-07-21 16:04:29.274 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
    2019-07-21 16:17:07.943 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
    2019-07-21 16:30:07.344 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
    2019-07-21 16:32:07.703 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 1080 (Device 0).

    2019-07-21 16:32:07.719 WARNING: ..\..\..\src\dzdynamicsengine.cpp(2956): ERROR: Memory Object Allocation Failure (-4)
    2019-07-21 16:32:07.828 Total Simulation Time: 48 minutes 23.52 seconds
    2019-07-21 16:43:36.724 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

    Post edited by mwokee on
  • Richard HaseltineRichard Haseltine Posts: 102,712

    There are various things that can cause an explosion - the cloth getting trapped between two intersecting body parts, for example, or unduly rapid changes in pose without increasing the number of sub frames in Simulation Settings.

Sign In or Register to comment.