Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0f1
Issue ID
1158778
Regression
No
Particle system is transformed incorrectly when using non-normal Scale values with ScalingMode.Hierarchy
To reproduce:
1. Open attached project "ParticleScaleProblem.zip"
2. Enter Play mode
3. Observe the sword of sample number 2
Result: particle system is deformed when scale axis are not equal to each other
Reproduced in: 2017.4.29f1, 2018.4.2f1, 2019.1.6f1, 2019.2.0b5, 2019.3.0a5
Note: for a workaround: add a parent to particles, which is an empty game object that has scale values that fix the ratio to be equal among all three scale axes
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:
This falls somewhere between "won't fix" and "by design".
There are known workarounds offered in the bug, and any changes to this code risk breaking other use cases for other users.
Ultimately, this bug is unfixable because the project uses camera facing particles, and we cannot know whether the non-uniform scale is intended to be applied in object space or camera space (because the answer is different for different users). We could offer more UI options to cover both cases, but it is a complicated area of code and the risk of causing other regressions feels too high.