Search Issue Tracker
Fixed in Unity 5.5.0
[Shuriken] Low-quality particle collision exhibits unintuitive behaviour
Low quality particle collision seems to "remember" the collider even after the collider is removed.
1. Open attached project
2. Open the ParticleSystem_Collision_LowQuality scene
3. Press play
4. Move "CollisionSprite" up to intersect with the particle system
5. Move "CollisionSprite" back down to no longer intersect with the particle system
6. Observe how the particle stream acts as if the collision sprite is still there.
Expected behaviour: Consistent behaviour with High/Medium quality or more information as to special Low quality behaviour.
- a quick chat in devs-particles suggested that "low" quality is for static objects.
- object tested in the scene is dynamic (perhaps adding information in the inspector that low quality works on static objects only and then disabling collision with dynamic objects could make it more intuitive?)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Crash in VCProvider when upgrading project from 18.3 to 19.1
- Android Vulkan corrupted rendering when there is no camera in the scene
- Array.BinarySearch parameters get swapped from .NET 3.4 to .NET 4.0
- Sort Order is not respected for a newly created Canvas until Play Mode is entered or any adjustments are made
- 'InvalidCastException: Specified cast is not valid.' errors are occurring when the Tile Palette window is opened