Sometimes it helps to be senile. I accidently imported a document without converting the text to a path first.
Loaded it in and said "Huh?"
I think with the release of 1.3.2 I "accidently" imported an Inkscape document with a spiral that wasn't converted to a path.
Again, I loaded it in and said "Huh?". That is when I discovered that it will take stars, ellipses, 3d Boxes, rectangles without converting to path first. Afterall - those are actually defined in SVG.
Fusion has gotten so good with SVG import that I don't even bother with DXF anymore. What is really fantastic is I don't even bother exporting out as "vanilla" SVG. Fusion will suck in those Inkscape documents directly with no issues. It can handle the transform matrix with no problems at all. So I use transform behavior set to "preserved" to prevent the dreaded "accumulated rounding" errors.
Note - if not saitsfied with the results of the path booleans you can always use the Shape Builder tool for more precise control how the glyphs overlap
Something has changed. Before - each individual glyph could be independently extruded. Now - the entire text is put in a text box and can only extrude the entire text.
Tyler - I really cannot "complain" about Fusion's SVG import. The developer handling that has really pushed the capabilites of SVG import the last 3 years.
Spirals, rectangles, ellipse/circle, polygons can be imported in without converting to a path first. It understands symbols. Now text from Inkscape.
The only issue is the import is still slapping a 96dpi scalar regardless of the units in the viewbox. Everything that Fusion needs for correct import is in that SVG viewbox. If the Inkscape document is using mm, cm or inch with a document scale of 1. Should be zero issues in proper scaling.
Ok - my mind has been completley blown.
Did you know that you can import Inkscape text objects into Fusion 360 DIRECTLY WITHOUT CONVERTING TO A PATH FIRST?
Ok - ready for the next quake? Every font I threw at Fusion worked!
I must have been in a coma the last 2+ years. Anyone know when this became possible?
Did not know that!
Sometimes it helps to be senile. I accidently imported a document without converting the text to a path first.
Loaded it in and said "Huh?"
I think with the release of 1.3.2 I "accidently" imported an Inkscape document with a spiral that wasn't converted to a path.
Again, I loaded it in and said "Huh?".
That is when I discovered that it will take stars, ellipses, 3d Boxes, rectangles without converting to path first. Afterall - those are actually defined in SVG.
Fusion has gotten so good with SVG import that I don't even bother with DXF anymore. What is really fantastic is I don't even bother exporting out as "vanilla" SVG. Fusion will suck in those Inkscape documents directly with no issues. It can handle the transform matrix with no problems at all. So I use transform behavior set to "preserved" to prevent the dreaded "accumulated rounding" errors.
Ok - now I am really impressed. Not only can you directly import any text, you can go back into the sketch and edit the text directly.
Update: Some script based fonts in some cases will have to be converted to paths. Anything where glyphs overlap.
In v1.4 Path>Union
Note - if not saitsfied with the results of the path booleans you can always use the Shape Builder tool for more precise control how the glyphs overlap
Last Fusion update killed it😯
Working here...
Fusion 2.0.20981 x86_64
Active Plan: Subscription
Windows 10 Pro 22H2 (19045.4170)
Thanks Tyler - let me check again. Might have been a loose nut behind the keyboard.
Something has changed. Before - each individual glyph could be independently extruded. Now - the entire text is put in a text box and can only extrude the entire text.
In this example - previously I could select each individual profile or do a window select to select everything.
Can't anymore. And - you cannot edit the imported text as before.
What version of Fusion did they
shove onpush to you?Fusion 2.0.20981 x86_64
OK - now in Fusion I have to select the text - right click for context menu - select "explode text".
I can accept that change.
Tyler -
I really cannot "complain" about Fusion's SVG import. The developer handling that has really pushed the capabilites of SVG import the last 3 years.
Spirals, rectangles, ellipse/circle, polygons can be imported in without converting to a path first. It understands symbols. Now text from Inkscape.
The only issue is the import is still slapping a 96dpi scalar regardless of the units in the viewbox. Everything that Fusion needs for correct import is in that SVG viewbox.
If the Inkscape document is using mm, cm or inch with a document scale of 1. Should be zero issues in proper scaling.
I currently use this method as a template: https://maakplek.nl/wiki/doku.php?id=from_inkscape_to_fusion_without_scaling_issues