-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several display issues when drawing paths #15
Comments
Hey @JustASquid, thank you for the report and the example. There are several issues in this svg and it would be really great if you could further simplify the svg. (and having it demonstrate just one problem to start with) Remove as many elements as possible, simplify elements and remove unneeded tags and attributes from the xml - using inkscape "plain svg" provides a better starting point when poking inside the xml tree. Could you do that? |
Hi Florian, thanks for your response. My first thought was to simplify the image by removing elements, but it seems like removing elements actually causes the issue with the brown section to stop happening. Are there any other specific issues with this SVG I can resolve? It was just generated with an online tool so i guess it's possible that it's ill formed, but all other SVG renderers handle it fine. |
@JustASquid what is the copyright status of this svg? We would want to have an example that we can include within our git to reproduce the issue and have an test case. |
I made the original image so it's free to use. |
@FlorianLudwig Just pushed an update to save the test image as simple SVG instead of Inkscape SVG. |
I'm trying to display the following SVG image (The actual SVG is in the reproduction below):
This is how the image is displayed in PIXI using this pixi-vector-graphics:
Notice the obvious visual glitches. I've attempted to make a more minimal reproduction with a simpler image, but at least the most obvious issue (with the brown section) seems to go away once certain unrelated image elements are deleted.
I've created a reproduction of the issue here.
The text was updated successfully, but these errors were encountered: