-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Holes in parts are not staying within the part. #191
Comments
DXF works fine! its so only a svg problem exported from inkscape DXF R14 |
Thanks for the response. However, as I stated earlier, this issue is also occurring with the DXF version of the output. |
Then fix the Issue and make all forms a path. So you should not have the problem. |
If I knew where the issue was with the exported file, I wouldn't be asking for help here. Making "all forms a path" is found where? Before I export? After I export (and in which recommended software?) Seriously confused by your intended verbiage of help. Could you explain it better in a "dumbed-down" version for me, please? REPEAT |
@StevenMarston |
First off, let me say this is an amazing piece of software!!
I have parts to be nested that have holes in specific locations. I've grouped the perimeter of the part and its hole prior to exporting from LightBurn. Inkscape and other software shows the holes are in place as needed.
However, upon importing the SVG or DXF into DeepNest, the holes become disconnected and are placed outside of the part. (Does the same for SVGnest).
Need the holes to stay in their location as having to put them back in place after the parts have been rotated and moved is far too much trouble. Doable, yes, but difficult.
UPDATE:
I'd read somewhere that DeepNest can be finicky at times and trying your file again might make it work.
I did so and after 4 or 5 tries, it managed to give the proper outcome. Good for now, but would like to have it working properly more often than lot.
BTW, did I say I really appreciate this project?
Probably more than you know. Thanks to all the developers!
The text was updated successfully, but these errors were encountered: