To diagnose the issue, people would need to inspect the SVG and your module code. Share it somewhere or provide a link to your repo, and we can probably quickly determine what the issue is.
Possible issues:
Wrong path or wrong letter case in the path in the SVG loading code (this is usually the createPanel call).
ViewBox <> Height, Width. The View Box is ignored by nanoSVG, so the scaling it does that you see in other means of viewing the SVG won’t be applied, and often this moves everything off your panel.
Using SVG elements unsupported by nanoSVG. See SVG-limitations
Or - just make them in a single tool and don’t try to move SVG between different tools. If you make it all in one tool it’s simple. If you are an SVG expert like @pachde , then it’s also easy.
I was just practicing using a module I’ve downloaded here to try to figure out how it works… I know some vendors/creators don’t want people modifying their work.
Is there a module or set of modules it’s OK for us to modify, as far at the artwork goes?
I’ll just recreate my steps from that. Don’t want to step on anyone’s toes, as the saying goes.
As long as you don’t re-distribute, no one will care. Also, as long as the license doesn’t prohibit it, you can do it. Library has other rules, but you aren’t going to re distribute.
By native, do you mean the “core” modules, or the fundamentals? Either way I think you would be fine. I’ve certainly seen ppl do that. But I’m just me, and don’t know anything special about vcv, so don’t take my word for it. For sure don’t modify those and re distribute. Posting images is ok, I would think.
And there is also something wrong with the rings around the knobs, they should not be filled. And the wet / mix in not visible. I think AI is just too much trouble…