Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.3.0b1
2017.3.0f3
Issue ID
985049
Regression
Yes
Particle Collision not detected when Particle System is negative in scale
To reproduce:
1. Open attached Unity project "ParticleCollisionBug.zip"
2. Open "demoscene" scene
3. Go into Play mode
4. Inspect the particles colliding and bouncing
5. Click "Mirror" which sets particle system's x scale to -1
Expected result: The particles should collide with the platform
Actual result: with the scale set to negative, particles ignore the collision (see attached gif "particles.gif")
Regression first introduced in: 2017.3.0b1
Not reproduce on: 2017.1.2p4, 2017.2.1p1, 2017.3.0a7
Reproduced on: 2017.3.0b1, 2017.3.0p1, 2018.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
- Bounding Box Size of Light Probe Proxy Volume and Settings.Max Interaction Distance of Panel Input Configuration Components cannot be added as Properties in Animation window
Add comment