They seem to pretty reliably come into F360, the problems are all later. That makes it a little hard to demonstrate with just the file. I attached an SVG that is one of these “ok now, wait until later” instigators.
- I cannot, for the life of me, figure out how to move/scale an imported SVG after initial import. Something about them doesn’t work like other objects. I can scale and move DXF after insert, but not SVG.
- You can stick them in a sketch, which is great. You can then create geometry from them via push/pull, which is again great. This is where things start to come apart though. Because you can’t move the inserted SVG geometry in the sketch it turns into a lot of extra fussing with the initial insert.
- Generating CAM operations (usually after changing parameters) very, very, frequently results in a crash. This doesn’t happen with geometry in the model that is exclusively “native”, and DXF derived geometry seems better behaved as well (ie. no crashes). I crashed F360 probably 50-60 times over the course of a couple days messing with toolpaths against SVG derived geometry. The problem is particularly bad if you adjust a sketch/geometry, then go back and regenerate the toolpaths. Learned to -always- save before regenerating the toolpaths or changing a toolpath parameter.
- DXF derived stuff appears better behaved - I haven’t done as much, but it hasn’t blown up yet. DXF’s off of “problem” SVG worked fine.
ps. I found “https://convertio.co” which does a better job for me that some of the other web services for file conversion, and free.