Can't "open" with seam info using .pacx files?
Hi,
I'd like to use CLO3D to simulate patterns which were generated computationally, including computationally-generated seam correspondences (that is, without having to hand-mark the seam segments). In other words, I would like to <i>either</i> A) use the python API to manipulate pattern geometry within CLO, or B) import a pattern using a format that includes seam data.
I get the impression from the API documentation and https://support.clo3d.com/hc/en-us/community/posts/360046103474-CLO-API-scope that option A is not possible. I considered trying to generate pdf files with different colors on the lines and writing a script which sews the matching lines, but I can't figure out how to access line color from the API.
Option B seems like it should be possible with the .pacx (file>save as>Pattern) file format, since when I view a .pacx file, it is a nice xml file that includes information like "SeamLinePair" data. However, I find that when I "Open" a "Pattern," all the seam info is gone. (Frankly, this feels like an error, because why does the file even include the information if CLO3D ignores it? Maybe it's a feature for future releases?) The seam info is apparently only imported from a .zpac or .zprj file, but these formats are compressed and undocumented, and therefore inaccessible to manipulate computationally. I see that https://support.clo3d.com/hc/en-us/community/posts/360028167194--pac-file-specification talks about this as well.
Is the lack of seam info support in .pacx files deliberate, or might it be fixed? Are there any other approaches which might work? Thanks for any tips or directions I might look in!
-
You can import DXF AAMA CAD data, that included the seam data from the perspective of the prior CAD notch location and polyline data that is mapped to the CLO3D default mesh particle distance. This means the incoming polyline data is referenced and then translated into layers according to DXF-AAMA standard. So you need to also ensure the integrity of the data when it comes out from the previous software, as you are dealing with an export and an import procedure. When an imported poly-line forms a closed shape, there can be a post process applied for the mesh density, so that is a transnational issue you need to keep a tight focus on between both apps. For example although a previous native app may have additional seam data to help make seam calculations more easy in the software (eg: xrefs) that may be dumped on export as it's only the DXF-AAMA datalayers that are being exported and to the polyline resolution. Generally that means the DXF-AAMA standard is your data transport limitation on what that includes so you need to look at that output from the previous software. I know with the Fashion CAD app(s) that I use prior to MD/CLO3D that some of the nice xref features for notch geometry and seam matching get dumped as part of the DXF-AAMA export process. Meaning I don't get to pick up on all that extra geometric information from my previous native CAD app (eg: seam type terminators which are generally scale dxf block inserts ) which is so handy. However in general if you get a good DXF-AAMA file out you can get a good DXF-AAMA file into CLO3D, which should include all the seam data, notches and dart insertion points etc.
DXF-AAMA is generally driven by layers associated to the allocated fashion CAD detail closed shapes > see the standard for that. So a DXF line type may be associated to layer designation, and of course the closed shape 'block' type (hierarchy). And that may be as much as you get in terms of ability to change line color as they are closed shapes and not necessarily independent (exploded) poly-line edges. So inside CLO3D you would have to look at the additional attributes associated to the sewing edge matching which is perhaps not done on import that is potentially only done manually after the basic pattern is imported (eg: within the CLO3D ecosystem) . eg: that the sewing edge data is stripped out from a prior app, as that is often not part of DXF-AAMA as it is generally only concerned with printable CAD patterns and layer designation for closed shapes or reference insertion points for 'blocks'. So potentially a stumbling block for your exchange process between apps. Maybe check with CLO3D developers to see if that possible to pick up on sewing edge data within their software from a DXF-AAMA exchange import. I would think that highly unlikely, as those attributes are most probably domain space (software) specific.
1
评论