Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.3.4f1
Issue ID
790595
Regression
Yes
[Shuriken/WebGL] Particles ignore collider in WebGL
Steps to reproduce:
Project:
1. Open attached project
2. Open the 'DemoScene2D' scene in 'Assets/WeatherMaker/Demo/'
3. Build and Run with WebGL Player
4. Toggle 'Rain' or 'Snow' and increase the 'Intensity' slider to maximum
5. Notice that the particles collide with the mesh appropriately
6. Toggle 'Collision' off and on again
7. Notice that the particles are no longer being generated when 'Collision' is on
WeatherMaker Demo:
1. Open http://demo.digitalruby.com/weathermaker/demo3d/
2. Toggle 'Rain' or 'Snow' and increase the 'Intensity' slider to maximum
3. Notice that the particles do not collide with the ground and the WebGL player starts to stutter
Expected: When 'Collision' is toggled on, particles stop when they collide with the ground and fade away
Not reproducible: 5.3.4p4, 5.4.0b11, (cannot test other versions due to WebGL incompatibility with browser)
Regression: from 5.4.0b14 to 5.4.0b15
Reproducible: 5.4.0b15, 5.4.0b16
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