Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1122698
Regression
No
SVG can't be used in Particle System when import setting "vector sprite" is used
How to reproduce:
1. Open attached "svg_image_issues.zip" project
2. Open the "Octopus" Scene
3. Go to Hierarchy Canvas -> SVG Scene -> Octopus Character Root
4. Go to the Inspector -> Particle system -> Renderer and observe that any SVG can't be set
Expected result: Particle System should have either render mode that accepts SVGs directly or SVGs mesh data should be useable directly with MeshRenderer
Actual result: Any SVG can't be set
Reproducible: 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Notes:
- In order to use SVG there should be imported "Vector Graphics" package
- SVG package is available in 2018.1 and later
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Hi, we have evaluated how feasible this would be to support, but unfortunately it would be quite complicated, therefore have decided that it is not urgent enough to proceed with. The Particle System is not receiving new features anymore due to the introduction of the Visual Effect Graph. Support for Sprites (including SVG's) may exist in that package in the future.