Spencer C. Imbleau

@seabassjh

Merge conflict @cpetzold

Superseded by #68

I'm a little concerned about overhead performance, personally. We export vello, https://github.com/loopystudios/bevy_vello/blob/d25d787f14c77533b9b038ad153847b0f13e1c46/src/lib.rs#L20 Which, vello will export `peniko`, `kurbo`, etc. In other words: - `bevy_vello::vello::peniko` - `bevy_vello::vello::kurbo` This gives you the...

Can you give an example? Because currently, the `bevy` types are used for the most part. I think you should only need `peniko`, `kurbo`, etc.. when you build or encode...

Good issue! Bevy-Vello uses 2 backends for rendering. Lottie: vellottie SVG: vello-svg The Lottie is significantly further in development than the SVG counterpart and because SVG is a monster, there's...

I forgot to mention another technique I commonly do, if all else fails. You can use the Lottiefiles.com tool to convert SVG to Lottie: https://lottiefiles.com/svg-to-lottie. The lottie backend is more...

> I have a similar issue with a simpler file: > >   Please send the SVG string so I can see what SVG features are being used

> Wow github really wants to render it. I've uploaded it here: https://gist.github.com/kristoff3r/b1e510635363e95caa5511534277d6ba If I was to guess, I think `transform="rotate(-45)"` isn't handled by `vello-svg`, but should be. I'll work...

Yeah, it's in the CHANGELOG, but that might not be good enough. I'd be fine taking with a PR for this. As a result, versions were reset back to 0.1....