Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b4
Issue ID
1089544
Regression
No
[ParticleSystemForce] The force component collapses the field range onto itself after a seemingly random amount of time
Repro steps:
1. Open the ExternalForcesIssue scene from the attached project.
2 Leave the effect to preview for about a minute (issue reproduces between 5 sec and 1 min)
2b. Alternatively, if the issue does not reproduce within 5 sec, open the scene again.
A video is attached demonstrating the issue.
Notes:
- Not a regression; new feature.
- Very rarely, when the issue happens, the range will dramatically increase, instead of decrease.
- Toggling the particle system or the force field on/off does not fix the issue
- Changing any value on the force field fixes the issue, until it happens again.
- Happens both in edit and play mode.
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