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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment