-
Notifications
You must be signed in to change notification settings - Fork 116
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
.svg Files imported from InkScape have the wrong size. #502
Comments
Same is true for Adobe Illustrator |
Same with svg files exported from openscad. openscad code:
then render and export to svg produces the following svg xml
Then when it gets imported into Luban cnc and laser it ends up being 25.6 mm wide and 5.1 mm tall. Maybe the SVGs are just getting bound down to 1 inch at the greatest distance? |
Although as a user I can then just peek at the first few lines of the svg xml and take the width/height values and after adding to luban manually set the size of my drawn object. IDK if illustrator or inkscape have those xml fields in them but it may be worth checking. |
Of course they have them. This is just a silly bug in the svg importer - hope it gets fixed soon. |
Sometimes you need to spoon-feed a developer a test case and what you expect for a result so they can put that into some sort of unit test to make more resilient code. |
It appears that all laser file imports are too small? I just opened the "Laser cut gift box" test project on 3.12.3 and it was only 25.6x25.6mm. I also imported a dxf I had created myself and it was also much too small. |
I just did some testing of old versions and found that 3.8 is the last version which correctly loads the gift box project. Unfortunately that isn't able to correctly load DXF files from Fusion 360. Looks like I'll just give up on laser cutting precise dimensions until this is fixed. |
Indeed.. I'm using 3.8. because of that which annoyingly cannot store 3d print custom profiles :( |
@Pflugshaupt Is it occurs in v3.12.2? For storing 3d print custom profiles, this feature should be available in version 3.12.2 |
profiles is fine since 3.9, but I need laser cuts that have the right size so I never went past 3.8. I am waiting for this issue here #502 to be fixed. |
I just ran into the same (or similar) issue: I use FreeCAD 0.19 and Luban 3.12.3. When creating a SVG or DXF, the model is smaller when importing in Snapmaker Luban (a circle with 20 mm diameter results in a circle with 2,8 mm in Luban). Is this planned to be fixed in a future version, or is there any workaround - or something I do wrong? Thanks a lot! |
Additional information: I can confirm that version 3.8 works as expected. Scale is correct when I load the SVG from FreeCAD in Luban 3.8. |
I installed 3.13.0 and I have also an issue importing svg file in luban. It is to small but indeed you can resize but the bigger problem is that luban adds a whitespace around the object even if the source svg file has zero margin. This gives issues in resizing. you can not scale it to a size that is exactly the size of the source because of that margin. I tried with DXF, SVG and PNG (in Vector mode) all of them have a margin around the object. Please fix this otherwise we can not cut precise based on the source object. |
Some tests with inkscape en illustrator below (same path (except first) exported in a few different svg formats) EDIT: |
It's a bug introduced in v3.9.0, we are still refactor the SVG editor to fix it. |
Can confirm, Luban 3.13.1 importing .SVG for laser cutting, files saved in CorelDraw. Imports the entire file about an inch in size. I'm glad to know this is a bug, I am a brand new user and I thought this was a terrible program! |
Seeing that I reported this bug in October and it is still not fixed does make me feel it is a terrible program :(. It is easily the weakest point of the whole snapmaker package. The slicer is missing so many (cura) features, the cnc part is mostly a joke and lasering is crippled by this very bug that feels like it could be fixed in a few hours. I wished they would just abort this project and instead provide first class support for Cura/Fusion 360 and some laser engraving software. Luban wants to do too many things at the same time and fails at all of them in some way. |
I think its pretty clear that Snapmaker doesn't have the resources to give software the attention it needs either on Luban or the firmware. The pace of development is very slow even for important bug fixes like this. It would be great if they would partner with 3rd parties to provide licenses/support for other programs. I'm really interested in the rotary module, but I can't see how they're going to provide the software needed to use it well. I'm definitely not interested in paying full price to get 4-axis support in Fusion 360 for example. |
Around 1 month ago I have submitted a pull request for this: Not sure why it is not merged/fixed already - it is just 1 line change. |
I'm not one of their programmers and haven't explored their source code enough to tell if it is set up for unit testing, but speaking as a programmer in general I wouldn't take a one line change without unit tests for that area which break without the change and pass with it. |
Please check if the issue still occurs in v3.15.0. I'm closing this issue for now. |
Issue persists, and has been carried forward into V4. .svg files and .dxf files are incorrectly scaled by a random factor when being opened in Luban. |
This issue should be reopened. This is a huge bug. |
Was having same issue - Worked when I loaded original SVG into illustrator and re-saved with SVG 1.0 spec |
This problem exists in Luban 4.10.1 |
Confirm with faberc. Scale still not coming in correctly with 4.10.1. Please put some effort into this, accuracy matters to almost everything I want to do on this machine. I am honestly amazed that this has been apparently broken for so long.... |
Since version 3.9.0 and also in the 3.10.0 alpha, svg files using mm units coming from InkScape get much too small (about 4x) when loaded into Luban to laser cut. It was fine in 3.8.0.
The text was updated successfully, but these errors were encountered: