Hi everyone,
I've been encountering a persistent issue when trying to export a shirt with a zipper from Marvelous Designer to DAZ Studio. Despite trying various settings and export options, I keep losing vertices and faces between the open and closed states of the zipper. Here's a rundown of what I've attempted so far:
1. **Base MD Export**: I've tried numerous settings and export options.
2. **Maintaining Exact Settings**: Ensured consistency across all export attempts.
3. **Export Methods**: Used both "Thin" and "Thick" options, among others.
4. **Re-Simulation**: Simulated the garment prior to each export to see if it would help maintain the geometry.
Despite these efforts, I continue to face failures in maintaining the exact vertex and face details. Has anyone else experienced this issue or have any insights on how to prevent the loss of vertices and faces when using zippers in Marvelous Designer?
Any help or suggestions would be greatly appreciated!
Thanks!
To allow other folks to help better, write some more descriptions if your issue is related to technical issues.
- ● Marvelous Designer Version (ex: 7.1.111) : Most Recent version
- ● OS Type : Win 10
- ● Mac Model Name (for mac users only) :
- ● CPU : A5
- ● Graphic Card : 3060 12GB
If you need a staff member to look closer at your issue for technical support. Please contact the Marvelous Designer support team.
Hmmm. I just tried this on my end and it seemed to work with no difference in point counts. I am not too sure why this is happening to you
Thank you for your response.
I encountered an issue where the item would not honor the morph regardless of the export settings. A similar problem arose when creating a new item and providing PJCM support through GoZ and manual Blender adjustments. Despite working with the same item and its shape keys previously, DAZ suddenly recognized it as having new geometry. This issue began when GoZ unexpectedly displayed a pop-up message stating that the mesh was now a SubD upon re-import into DAZ.
I will continue investigating this as I develop new items. If I identify the cause of this error or determine a solution, I will document it here for the benefit of others.
For now, I am pleased to know that the functionality is achievable, as others have successfully implemented it. Thank you again for your assistance.
Please sign in to leave a comment.