Dear,

I have sadly new problem with inserting SVGs in any charakter model. It is not possible to add a SVG element in a charakter element. Failure window: "Failed to add element".
I also tried "plain SVG" and "optimized SVG" via Inkscape but it don`t work also. Also changing page px to 2048x2048 for example is not working.
Other formats like JPG are working (but I sadly want to work with SVG).
Adding/Importing a complete SVG charakter model is working correctly. But changing little parts, also I tried to import SVG in demo animals, like a new head - but sadly also not working.
Is there maybe some workaround?

Used Software:
Cartoon Animator 5.01 (newest version)
Inkscape 1.2.2

Failure adding Inkscape SVG:


Create sprite based head:


Inkscape page 64 x 59 px:


Have you any clue why SVG importing in CTA5 is not working?
Thank you in advance

I have imported raster images from photoshop to CTA5.
I have imported SVG from illustrator to CTA5
Today I have managed to import svg from Animate> illustrator> CTA5.
SVG is working just fine.
It is how you create a template and name the layers in the outside software that matters more.
If one word or letter is missing in the layer names of the template it is not going to work.

I am not so sure about Inkscape and other software because I use Adobe products, and even with that, it takes hours to create a custom template properly rigged.

Search for online tutorials. Rigging in CTA5 is a bit different than in CTA4, so that could be an issue as well.
Check out tutorials on 2danimation101.com. I got the courses for free with CTA5 and it has really helped me a lot with this rigging part.




CTA5, Iclone 7, 3D Exchange Pro, Character Creator 3, Popcornfx plugin, Zbrush, Blender, Vue 2014, Adobe cc suite, Spriter
Homebuild Workstation (Pretty old now but still working great) Win 10, Intel i7 950, 24 GB RAM DDR3, Gigabyte x58a-ud7 motherboard, AMD R9 390 sapphire 8GB VRAM.
Official Website  Reallusion Store  

@Framecraft, thank you for your reply.

After checking new release CTA 5.02 this bug is solved now.
Thank you to the dev-Team for fixing!
BR