dForce and Marvelous Designer

Hello, I am having a problem and have been battling for days without being able to resolve it. I designed my first piece of clothing in MD and exported the obj to Daz, applied the transfer utility, and dforce. It works perfect. The problem is when I apply stitching to the garment in MD and then apply gForce. It messes up everything. My clothing is exported as one object, which should includes the stitching. Am I exporting it wrong or why is dforce not happy when the stitching is applied on the garment?
Thank you so much for helping.
Post edited by Nelmi on
Comments
dForce, not gForce.
How it it messing up? If this is greatly increasing the mesh density, as I suspect it is, that will affect the way the simulation runs, and you may need to increase the number of sub frames and/or iterations per sub frame (in Simulation Settings) to avoid the mesh's "exploding".
Sorry, typo :) Without the topstitching it works perfect. Once the topstitching is added, it explodes exactly in the places where the stitching was added. When simulation first runs, it starts with a (Spring (***numbers***), until 100% and then starts simulating. It runs more or less until 22% and explodes. I will have a try with the sub frames and iterations per sub frame as you subframe as you suggest.
Yes, I have noticed that. So, how do I keep the topstitching and manage to use dforce? It is so tedious to do the stitching in PS and templates. I do not have Zbrush.
There are various tools, at least one free as I recall, which will take a high resolution mesh (such as the one with top-stitchin) and a low resolution mesh (the oen without) and bake a normal map for the latter from the former.
Thank you, I will have a look. I appreciate the help.