SnapmakerJS not translating SVGs properly


#1

Is SnapmakerJS so bad that it can’t even perform the simplest vector translation?.. This isn’t the first one that I get this. The only shape I could get it to translate properly was a simple hex.

This is my imported SVG:

And this is what I get after generating the GCODE and loading:

Can anyone help?


#2

LMAO!!! Snapmakerjs can perform simple transforms I can confirm, but there are still bunch of tags and attributes are not parsed and used in Snapmakerjs.

Please try the latest version of the software to see if it works for you, we’ve fixed some problems with the SVG parsing. If problems still occur, upload your SVG here and we will see what’s wrong with Snapmakerjs.


#4

Oh, I was using version 2.4.3, I didn’t realize the latest version was in the forum. Lets see if that fix the problems.


#5

So, still having problems. Check the screenshot:

Here’s the SVG I’m trying to load:
meepleguz

The curious thing is that this SVG, arguably more complex, loads without any problem:
teddybear

Thanks for the help!

BTW, this update has some really nice features. I hope this SVG translation gets corrected soon because cutting / engraving with vector is so much cleaner and faster! But anyhow, great work on the updates :slight_smile:


#6

@guzforster

Thanks for your file, it’s simpler than I expected.

Seems like it’s the problem of numeric parsing of SVG path. We’ll try to fix the problem ASAP and once it’s fixed we’ll let you know.


#7

Seems that this is going to take a while :slight_smile: Do you guys recommend any software for exporting SVG that SnapmakerJS could read without any major issues? For these exports I used Illustrator - if I use Inkscape or Sketch would it make a difference?


#8

I was running to the same problem so skipped the middle man. I am using this to generate the g-code http://www.scorchworks.com/Dmap2gcode/dmap2gcode.html. It is working really well for CNC still trying to find the perfect settings but the g-code generates clean and you can go straight from any image file skipping the SVG conversion.


#9

Thanks, but this program only accepts bitmaps files apparently, not vector ones - I’m not having any issues with bitmaps, my issue is with some vector files imported to the SnapamakerJS app.

@parachvte any updates on fixing this issue?..

Thanks


#10

Not really. Gonna release next version tomorrow, which includes updates for preview. And a bunch of SVG parsing issues are scheduled on next version.


#11

Cool, thanks for the update :slight_smile:


#12

Try this then it worked to get snapmakerjs to accept my vecor files. I think it had to do with the final save being an optimized CVS. https://m.youtube.com/watch?v=1cZk08x_rAI


#13

Isn’t it meant to be an Optimized SVG? I am curious if this will work better then, will try it this evening.


#14

Sorry yes spend too much time at work working with CSV and got my accronyms messed up.


#15

Sorry for the super late reply! I was away for a LONG time from 3D printing and laser engraving, but hopefully I’m back now with some projects to share.

Also I’m hoping that this issue is solved already, a lot of time has passed since it was posted… I will check that this afternoon.

And thanks for the link, I will also test that :slight_smile:


#16

So it seems no progress has been made on the front of actually making SnapmakerJS translating proper SVG files? Dudes, this has been almost a year already. This is just buggy and doesn’t work; can we get a patch for this please?..

All I’m doing is exporting the vector file as an SVG from Illustrator, which is a pretty common and standard software for vectors. That might help you guys understand the issue.

SVG file is attached for reference (and you can see that even this WEB VIEWER can parse the SVG correctly):

TIHIR