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
- 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
Add comment