Community
Fusion API and Scripts
Got a new add-in to share? Need something specialized to be scripted? Ask questions or share what you’ve discovered with the community.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

What makes different "kinds" of SVGs perform differently when being imported through the API?

0 REPLIES 0
Reply
Message 1 of 1
kgehrke58RYW
98 Views, 0 Replies

What makes different "kinds" of SVGs perform differently when being imported through the API?

I am trying to write a script that allows the user to import an SVG into a sketch and extrude it automatically. All SVGs can be selected via the file selection, however, I seem to have an issue where only SVGs created via a Python vectorizer are recognized by Fusion. When I use SVGs from elsewhere, sometimes it gives an error that says it does not have recognizable paths that can be extruded, and sometimes it is "TypeError: cannot unpack non-iterable NoneType object."

 

I put "kinds" in quotes in the title because I'm not sure what is going on behind the scenes with SVGs of different origins. SVGs I make in Adobe Illustrator and export as .svg files don't work and SVGs I download don't work. Only the ones made in the Python program work in the script.

 

Any insights as to what may be different about SVGs of different origins, or ideas on how to get Fusion to recognize all SVGs, regardless of where they come from?

 

Alternatively, does anyone know what settings in Adobe Illustrator to use when exporting as an SVG such that the SVG works in Fusion?

0 REPLIES 0

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report