Gradig .dxf + .rul from GRAFIS CAD software
Hello CLO team,
The issue I have as follows:
1. Patterns created in GRAFIS CAD software in .dxf and .rul for grading.
2. When imported in Clo3d some parts represented incorrectly as shown below. The grading itself works correctly.
3. Any suggestions on how to fix this highly appreciated!!!
Thank you in advance for your proposals for a possible solution!
Elena
-
I think this is one area that really needs to be expanded on in the knowledge base CLO3D.
2 -
Hello, ottoline! Thank you for level up this question up to the required knowledge base of in/out from different software.
I didn't mention what the constructor already did before I sent this request to QA CLO Community.
1. Checked that it did exported in DXFAAMA standard.
2. Checked the closed shape - shape is closed.
3. Change language settings in name files and description...in case.The issue is when the same pattern is used without gradings - it works ok. But when the grading appeared the problem arises.
p.s.
Can you send me a link to your own website for clients?)
Thank you!
Elena.
0 -
I think it's time that CLO3D set this up, as a proactive part of smoother datafile exchange workspace between systems.
1 -
Hello, Ottoline! Thank you for your comments! With a respect to your intellectual property and private data - I didn't want to jump into your privacy and secure server unless it's possible for outside users.
So, my issue solved as follows:
1. More detailed analysis of the pattern parts shows that the problem arises when there are buttons or other small decorative elements. Or in parts where reflection was done during construction.
So...
2. All additional elements were transmitted to the mark lines (not contour lines). The inner contour in the places where the reflection was made was matched. Were not to put some symbols (it is not completely clear, since the symbols are put in a closed figure and should not interfere).
Hope it helps smb. to prevent such problems and save time!
Thank you!
... will go further! ;-)
Elena
0 -
Check out the plugin - Clo-Vise for PLM maybe that is a service solution for smoother data-transfer.
0 -
Thanks, ottoline, for the link - yes, it interesting feature...under investigation by my team in terms of the protocols, etc. of transferring. But it's another type of data)) the next step of final or semi-final product but in this topic, we speak about zero-step of dxf -> CLO. Why you deleted your long exposes about its importance )) by the way?
p.s.
New day - the new challenge https://support.clo3d.com/hc/en-us/community/posts/900002096026-Button-garding1 -
I often delete long replies as a copy is generally posted direct to email to contributors in any thread and that is not so essential to other readers. That way a thread doesn't drift into paginated pages, over time, and I often leave the essential links, or points in place with more brevity.
If in doubt with DXF-AAMA open up an ASCII export version in any text editor app and you can read the DXF to see if the output is in compliance with the next app and with DXF-AAMA standards in general. That is always a belt and braces way to work through DXF exchange faults. And if you export a DXF-AAMA from CLO3D you can compare the ASCII text results with the previous app - that way you can calibrate your export process so they are both in sync for better data exchange.
Any reference in CAD (ie: zero point) is relative to the inherent way the euclidean space of the 2D and 3D world (paper space) may be set to that app drafting interaction and UI, this is usually easily adjustable and can also be scripted into your own custom translators to clean (purge) exchange code for 'xrefs' that sit in CAD data.These xrefs are a powerful way of manipulating drafting data relative to an app. eg: nesting, mirroring, instancing internal blocks, but how each software app treats these can be unique to their CAD system so often you need to double check these - eg: insertion points for symbol blocks (notches, button holes, darts).
0 -
Clear, thanks for DXF-AAMA exporting advice!
Elena
0
댓글