"Spring of node..." woes (dForce)
Tobor
Posts: 2,300
Is there any way ahead of time to determine if an article of clothing not already designed for dForce won't trip up the simulation with excessive "Spring of node" corrections? I can set A value to below the standard 0.20 threshold, but then I never know if the mesh needed it or not for a decent simulation. Also, some other settings particularly related to stretchiness alter the length value to well under 0.20.
It can be a real problem because there's no Cancel button for this popup. Yesterday I sat through 20 minutes (yes, really!) of error corrections, and no way to stop the process. Of course the simulation crashed afterwards. I've taken to simply shutting down Daz and restarting. A cancel button would be better, as well as some method of at least guessing if the mesh is going to be problematic. Ideas?
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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Cancel button. Pretty please! This is so annoying.
I don't want to be the "me too" guy, but... Yes... I'd like a cancel button too. Googleing this annoyance is what got me here.
OMGERD YUSSSS
Late to the party, but since I found myself in here for the same reason as others, yes, a cancel button would be much appreciated.
*raises hand*
Bartender, I'll take one of those also please.
In the year 2026, still wishing for a Cancel button for this process... As I write this I'm ~40 minutes deep into simulation of a ratchet strap around some wine barrels and only at 27% for spring of node 2554500+...
As has been explained in other threads on this topic, adding a cancel check would slow the process down even with wel-designed clothes - the pain when dealing with items not made (properly) for dForce is understandable but alleviating it would hurt all users even with well designed clothes.
Why couldn't they add code to just the error handling path? After X number of spring errors, pause and give the user the option to abort or continue. Well designed clothes without spring errors, should not be impacted by code that only gets executed when a spring error occurs. Nobody wants to wait for hundreds or thousands of spring errors. The chance of the simulation working after that is pretty low anyway, I think.
It has been a long time sine I have touched Windows code as such, but essentially there is an event loop that has to be handled (check to see if there are any commands sent on from the OS that the application needs to respond to). Juggling that in a very short loop, even inermittently, may well be complex and slow realtive to the actual operation being carried out on each loop. I simply can't guess whether a check every soe many edge checks would be workable, nor how much impact it would have on the whole process even in wel-behaved cases; I would think it highly likely that they considered such an option.
I don't understand how commands from the OS would be involved here. Isn't the check for spring errors performed totally inside the Daz Studio application? Those spring error messages sure come out rapidfire. I don't know anything about the coding of Daz Studio, so I'll just drop this now.