That's interesting, all my DXF files are made the same way, and I GOT BANNED from pee-spider so my only comment about that is a lot of the junkiest files I ever saw were there and any of my files still there may be considered to have been kidnapped by an extremist fanatical SignTorch hater/exploiter.... :blackeye:
There should be no difference in the files, except fonts are much simpler and much less detailed.
How are you "working with" them before sending them? In what software?
Are you modifying the super files in a way that alters them differently than the font files? An opened path or something could easily confuse a nesting program.
My files usually don't have any open paths, but "working with" them in certain ways can mess them up royaly.
Such as if you scale them asymmetrically, then the arcs become ellipses and that can cause all sorts of problems in all sorts of software depending on if and how the software handles ellipses and non-radial curves. Conventional CAD/CAM software plots them as a series of small line segments, and not necessarily in connected or closed paths, which may or may not work or behave differently or as expected in downstream software.
Does it give any indication why it won't nest?
The fonts are quite bold, the super files can be smaller drawings with thinner sections which must be scaled up much more so than the fonts to accommodate kerf, but it doesn't sound like you got to that point, unless nesting is automatically trying to apply kerf compensation during import and that plays into to the problem.
Can you post a file of whatever you're trying to send to nesting, whether it's gcode of DXF, so I can see what we're dealing with, and if there's any obvious un-nestable geometry?
