Search Issue Tracker
Fixed in 2018.4
Fixed in 2019.1, 2019.2
Votes
0
Found in
2018.3.0a4
2018.3.12f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1149364
Regression
No
Listed Force Field keeps affecting particles when its GameObject is active and Force Field component is disabled
How to reproduce:
1. Open the attached project ("ParticleSystem_ForceField.zip")
2. Open the repro scene ("Main")
3. Enter Play Mode
4. Inspect the behavior of particles
Expected results: Disabling Force Field component or its GameObject disables the Force Field effect
Actual results: When the GameObject is active, but its ForceField component is disabled, the Force Field keeps affecting the particles
Reproducible with: 2018.3.14f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a1
Couldn't test with versions prior to 2018.3.0a4 as they lack Force Fields
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Hub] Editor is shown in the "Installing" state indefinitely when the installation fails due to INVALID_DESTINATION error
- Searching packages on an ill-configured scoped registry targeting Google Unity API registry throws an error
- Not possible to deduce the source of 'Shader properties can't be added to this global property sheet.' error
- [MacOS] Mouse input gets interrupted when changing values in inspector by dragging mouse
- Adding/removing components expands collapsed components view in the Inspector window
Resolution Note (fix version 2018.4):
Fixed in 2018.4.2f1, 2019.1.6f1, 2019.2.0b4, 2019.3.0a4