Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.3.0f4
Issue ID
754014
Regression
No
[Shuriken] Low-quality particle collision exhibits unintuitive behaviour
Low quality particle collision seems to "remember" the collider even after the collider is removed.
Repro steps:
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.
Notes:
- 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.
Latest issues
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
Add comment