Search Issue Tracker
Fixed in 2018.4.X
Fixed in 2019.1.X, 2019.2.X
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2018.4):
Fixed in 2018.4.2f1, 2019.1.6f1, 2019.2.0b4, 2019.3.0a4