Dumb question but did you check the settings to see if you are using multiple passes?
I haven’t looked at the svg so I can’t say if it’s the file.
1 Like
I don’t think that is it because it was doing it the other day too, and I don’t think I would have accidentally set the one file to two passes TWICE. plus, I don’t think it is easy to accidentally change the passes. and I know I didn’t do it on purpose.
So this file is a nightmare of bad nodes and other cruft.
I don’t know where you got it, but it’s really not well made for lasering. There are enough stray and extraneous nodes that I wouldn’t even try to work with it without serious cleaning up/redrawing.
My point is that I don’t trust the svg at all so I wouldnt be surprised if it has some weird edge case bug that is causing it to either run twice or appear that it is.
First off, try using “clean up document” under the file menu and save a new copy. It’s not likely to save you, but who knows.
I might also try copying and pasting the paths to a new document and resaving with a new name and trying that one.
5 Likes
I was just looking at it, too…(not in Inkscape) and agree about all the extra nodes, but other than that I couldn’t see anything doubled up. Is there any chance that you could have loaded it into the UI twice and they landed on top of each other? Or that you maybe added it into the UI separately again like through the add art button?
oh no 
… I’m kind of committed to a project using this. what makes a file a nightmare of bad nodes?
I will try to clean it up.
I did say it was a dumb question. It’s worth looking because if that is the reason it’s a very easy fix.
But again, your svg has a hundred other problems that I’d worry about first. The details on the leaves are too small to resolve, there are two leaves that are separated by 0.003", which is thinner than kerf and is going to lead to overburn and is possibly a fire risk (too much laser dwell time in one area).
Oo, yeah that’s a good thought too. But you’d probably know it if you did that because you’d see two jobs on the left.
2 Likes
well clearly I have a lot of work to do here!
I took a screenshot of one of the bad areas to show you;
If you can simplify the lines it will help immensely, though don’t know that it will solve the initial problem of it cutting twice. Good luck!
If I simplify the tree, then mary becomes a big blob on a donkey. this is a nightmare. LOL.
Here’s a zoomed pic of the path with nodes on.
Problems:
1: Extra junk nodes floating in space.
2: Lines far too close together, it’ll burn that section off.
3: Weird “jitters” in the path, it won’t go well.
4: Extra nodes for no reason, it’ll go badly.
5: A couple of weird “loops” or islands. Also will go poorly.
I just whipped through it, this is a very zoomed tiny fragment, and isn’t even all of them in this view by a long stretch. This is typical of the types of problems you run into when you get SVGs online. You usually have to do a bit of cleanup, but this is a pretty bad example.
5 Likes
well boo… Is there anyway to remove nodes individually instead of “simplifying”.
Yup.
I suggest you get super familiar with node editing in general. In fact, I posted about this before:
4 Likes
This much editing will take you hours. If it were me I might look for new art that is similar and either trace a raster or verify the quality before trying to cut it.
This sort of religious silhouette is really common, there are no doubt other very similar derivative works (this one is in itself pretty derivative). I bet you can find something that works better.
4 Likes
okay, you guys are great. you teach me so much. when I saw a file before with lots of nodes I was like “wow, that’s really complicated”. Now I realize more often than not, it’s just badly done, probable by some computer program because people were too lazy to do it right and edit. I redid this myself using the …um…bezier…tool I think it is called, and it cut so much more nicely and when you click on it, it
doesn’t look like somebody went ham crazy with nodes. thank you for teaching me what to look for. I feel like I learned something so important today. I had no idea this was a trash file, but when I
looked at all the screen shots you sent me and stuff I realized how messy it was and i can’t believe i paid money for it!!
7 Likes
I skimmed through but didn’t see that it resolved your cutting twice issue.
Either paths/objects are doubled up on top of each other (which doesn’t appear to be the case from the screenshots), you are setting two passes in the app (which doesn’t seem to be the case), or, the stroke has been aligned to the inside or outside (but not center).
If the stroke is aligned to inside or outside, it essentially expands the stroke in the app, causing a cut line on the inside and outside. It needs to be center aligned.
An Inkscape expert or google search can probably show you how to check and change this.
2 Likes
I did a quick cleanup to see if it made a difference and whatever change I made seemed to clean it up and it only ran once. Don’t know what it was though. 
If you run the image too small all those palm fronds will make your GF kick like a mule so keep it in mind.
sd2.zip (7.1 KB)
(missed a few nodes and and wanted to smooth out some tight angles so fixed it again.)
4 Likes
Will this image work?
4 Likes
I often have such issues especially when I have used the trace function. It really is not so hard to wander down a line in node mode and just grab everything between two nodes you want to keep and just hit delete. As @evansd2 noted you don’t want lines 0.0003 apart anyway so a bit of deleting and moving the occasional node can clean it right up…
If there are 50 nodes between two points less than 1/16 of an inch apart it really does not matter what is going on as it will never show up anyway. If it scales really huge then you might remove fewer nodes but if you set the scale you are going to use and then which nodes need removal will be easy to see.
1 Like
This topic was automatically closed 32 days after the last reply. New replies are no longer allowed.