Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0a7
Issue ID
947417
Regression
No
Particle system collision gizmos are also shown for particles without collision module when multiple particle systems selected
To reproduce:
1. Create new project
2. Create two particle systems, reposition one of them so they wouldn't stack on each other
3. In one of the systems, enable and expand collision module in Inspector window
4. In hierarchy window, select both of the systems
Expected: collision gizmos only shown for particle system with collision enabled and expanded
Actual: collision gizmos shown even for particle systems that do not have collision module enabled (check .gif attached)
Reproduced in: 5.6.0f1, 5.6.3p2, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
Not reproduced in: 5.5.4p4,5.4.6f3, 5.6.0b11
Regression starts in: 5.6.0f1
Note: issue is partially present in all tested versions. If in step 4 first selected particle system is the one without collision module
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