dForce on 2 items in the same model [Solved, but why?]
richardandtracy
Posts: 5,898
I wonder if someone could show me where I am going wrong.
I have one of Arryn's dForce dresses, and Linday's dForce side layered messy hair. Both work independently, but if I have the two in the model at the same time, the dForce simulation goes for 11 seconds and then the Nvidia driver crashes. I don't think it's a memory issue, have a 16Gb Ram machine with a 6Gb GTX1060 and the latest stable driver. The scene is empty except for a G8F character, hair and the dress. No fibremesh body hair or anything else.
I have tried running the dress simulation, then setting the dress as a static surface, adding the hair, and trying to simulate that. Result: the driver crashes.
Does anyone have any suggestions?
Regards,
Richard.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Select all the surfaces and see what the Collision Layer is - each item should have the same value, but the two items should have different values.
Richard,
I had a look at it. The collision layer for the hair was all layer 1. 3 of the four surfaces in the dress were layer 1, with the cape layer 2. I changed all the dress to layer 2, and it died.
I then restarted DS, and left the dress alone, turning the hair to collision layer 3. At 11 seconds, the driver died.
Regards,
Richard.
Same happens replacing Arryn's Dianne dress with Arryn's Jasmine Dress.
Regards,
Richard.
Went a bit further, deleted the hair, and the simulation failed. Re-loaded the duf file, deleted the dress and the simulation failed. Re-loaded the .duf file, deleted both, added each as a separate asset, trying to simulate each separately, it worked. Then loaded the two together, and it failed.
The two really don't want to get along.
Tried deleting the simulation modifier from the dress. The hair simulation failed.
Gaah!
Regards,
Richard.
I think you've run out of VRAM on the GPU. Open task manager and observe usage when trying this.
Unfortunately, the machine is Win7 & the vram isn't shown in task manager.
I suppose that means I'll have to do the simulation for each separately and save as an object file and reload as a morph. No, that won't work, as it has the pose in the object file.
Oh, how frustrating.
Richard.
Edited to add: Think I now know how to get the morph into the model properly. Will try it next year (ie tomorrow!)
@richardandtracy_e725004c1a
Use GPU-Z to monitor youe GPU.
Thanks, got it.
Regards,
Richard.
You'll be having more troubles once Windows 7 end-of-life software cycle hits on January 14 this year. Support for Windows 7 ends with MS very very soon.
The machine isn't connected to the web or any other home network (for that very reason), and hasn't been since I got it last March. I transfer everything to it via a memory stick. While it's not very efficient, the machine works well, and I am pleased that it's now safe from MS updates that have a chance of correcting the fact it works well. I'm using DS 4.11, more from inertia than the belief 4.12 won't work. I shall be wary of future updates beyond 4.12, and will keep installation files of the previous version just in case.
Having loaded GPU-Z, and watched what happened just prior to the driver crashing, the VRam usage didn't get much above 3.6Gb, so I must conclude that the two models just don't like each other.
Regards,
Richard.
I managed to get the simulation to work. Instead of having the figure return to a saved position, I simply turned that part of the simulation off. And it worked.
I am pleased but baffled. Why would this make a difference?
Regards,
Richard.