"Error preparing objects to simulate."

LosingSignalLosingSignal Posts: 409
edited October 2018 in The Commons

Okay, so I set a scene up with a character (Corin by Mousso), an environment (Tree and Swing Set), and dForce Casual Country Girl.  Pose it up, hit Simulate for the dForce stuff, and I get the ["Error preparing objects to simulate."] Title message.  According to my log file, it looks like something might be wrong with my dForce kernel?  Maybe some model interaction issue?  Or is this a Support Ticket issue?  Has anyone else had a problem like this and fixed it?

2018-10-13 09:45:37.024 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_MAP_BUFFER on GeForce GTX 1070 Ti (Device 0).

2018-10-13 09:45:37.025 WARNING: ..\..\..\src\dzdynamicsengine.cpp(2301): ERROR: clEnqueueMapBuffer (-4)
2018-10-13 09:45:37.265 Total Simulation Time: 3.63 seconds
2018-10-13 09:46:03.842 Loaded image PBMAbsHeightRSWM.png
2018-10-13 09:46:03.842 Loaded image PBMAbsHeightRSWM.png
2018-10-13 09:46:03.867 Loaded image CTRLAnconeusSWM.png
2018-10-13 09:46:03.871 Loaded image CTRLAnconeusSWM.png
2018-10-13 09:46:03.873 Loaded image PBMAnconeusLSWM.png
2018-10-13 09:46:03.874 Loaded image PBMAnconeusLSWM.png
2018-10-13 09:46:03.875 Loaded image PBMAnconeusRSWM.png
2018-10-13 09:46:03.894 Loaded image PBMAnconeusRSWM.png
2018-10-13 09:46:03.919 Loaded image CTRLBicepsSWM.png
2018-10-13 09:46:03.919 Loaded image CTRLBicepsSWM.png
2018-10-13 09:46:03.933 Loaded image PBMBicepsLSWM.png
2018-10-13 09:46:03.934 Loaded image PBMBicepsLSWM.png
2018-10-13 09:46:03.936 Loaded image PBMBicepsRSWM.png
2018-10-13 09:46:03.959 Loaded image PBMBicepsRSWM.png
2018-10-13 09:46:03.981 Loaded image CTRLBrachialisSWM.png
2018-10-13 09:46:03.982 Loaded image CTRLBrachialisSWM.png
2018-10-13 09:46:03.984 Loaded image PBMBrachialisLSWM.png
2018-10-13 09:46:04.003 Loaded image PBMBrachialisLSWM.png
2018-10-13 09:46:04.005 Loaded image PBMBrachialisRSWM.png
2018-10-13 09:46:04.005 Loaded image PBMBrachialisRSWM.png
2018-10-13 09:46:04.034 Loaded image CTRLCaracobrachialisSWM.png
2018-10-13 09:46:04.034 Loaded image CTRLCaracobrachialisSWM.png
2018-10-13 09:46:04.054 Loaded image PBMCaracobrachialisLSWM.png
2018-10-13 09:46:04.054 Loaded image PBMCaracobrachialisLSWM.png
2018-10-13 09:46:04.056 Loaded image PBMCaracobrachialisRSWM.png
2018-10-13 09:46:04.057 Loaded image PBMCaracobrachialisRSWM.png
2018-10-13 09:46:04.074 Loaded image PBMDeltoidAnteriorRSWM.png
2018-10-13 09:46:04.075 Loaded image PBMDeltoidAnteriorRSWM.png
2018-10-13 09:46:04.088 Loaded image CTRLDeltoidAnteriorSWM.png
2018-10-13 09:46:04.089 Loaded image CTRLDeltoidAnteriorSWM.png
2018-10-13 09:46:04.093 Loaded image PBMDeltoidAnteriorLSWM.png
2018-10-13 09:46:04.094 Loaded image PBMDeltoidAnteriorLSWM.png
2018-10-13 09:46:04.112 Loaded image CTRLDeltoidMiddleSWM.png
2018-10-13 09:46:04.113 Loaded image CTRLDeltoidMiddleSWM.png
2018-10-13 09:46:20.119 File loaded in 0 min 0.3 sec.
2018-10-13 09:46:20.152 Loaded file: CCG !Outfit.duf
2018-10-13 09:46:26.436 WARNING: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_MAP_BUFFER on GeForce GTX 1070 Ti (Device 0).

2018-10-13 09:46:26.439 WARNING: ..\..\..\src\dzdynamicsengine.cpp(2301): ERROR: clEnqueueMapBuffer (-4)
2018-10-13 09:46:26.679 Total Simulation Time: 3.64 seconds

Post edited by Richard Haseltine on

Comments

  • Does it simulate from the base pose, assuming it isn't already trying that (if you have the simualtions tart from the memorised pose and that is the zero pose)?

  • L'AdairL'Adair Posts: 9,479
    edited October 2018

    ETA: I reread the OP, I think the error message I've seen is dfferent from the one mentioned. I'm leaving up the rest of the post, in case it is helpful to someone else reading the thread. The message I get is more like, "No dForce objects found" to simulate.

    @LosingSignal, I've seen that error message a number of times. Here is a list of things I've discovered will cause that a no dForce object found error when nothing else is wrong.

    1. Not all the wardrobe items on the figure are dForce ready, and I've hidden all of the items that are.
      • This seems to be getting more common with dForce compliant clothing sets, I think, where a shirt and/or jacket of an outfit have dForce applied but pants do not. Or a skirt will have it and the top does not.
    2. I've simulated an object, cleared the simulation, changed the pose a bit and resimulated several times. Suddenly, it stops working and throws that error message.
    3. In the case where I'm using clothing that wasn't sold as dForce compliant, I forgot to add the dForce modifier.

    For item 1, make sure the item(s) with the dForce modifier are visible. (You can do them one at a time, if you like, and set Freeze Simulation to On for each as you go.) For items 2 and 3, go back and add the dForce Dynamic modifier. For item 3, if adding back the dForce modifier doesn't fix it, save the scene, close Daz Studio, reopen DS and reopen the scene. And then select the object and apply the Dynamic dforce modifier. Save immediately.

    Post edited by L'Adair on
  • Does it simulate from the base pose, assuming it isn't already trying that (if you have the simualtions tart from the memorised pose and that is the zero pose)?

    I tried it from the base pose and it simulated fine there, but any other pose I would get the error message.  I tried erasing the whole scene, restarting Studio, then setting the figure back up.  It would simulate from the base pose, but now any pose would make the sleeves jump off the figure and simulate along the figure's back.  Next, I erased the figure and tried just a base Genesis 8 Female character and the clothes.  It seemed to work fine, so I went back to the original figure, where the clothes now just exploded with any pose.  After erasing and reloading again, the clothes now seem to simulate fine.

    So, I guess... problem solved?  I'm just puzzled what could cause this.  Software should be more consistant in its errors than this.

Sign In or Register to comment.