Search Issue Tracker
Particles affected by a ForceField behave differently when in Edit/Play Mode and Player
1. Open the attached project “ParticlesForceField”
2. Open Scene “Assets/_Workspaces/Tests”
3. Select the “SaltDispersionParticleSystem” GameObject located under “Jar” GameObject.
4. Observe the particle effect (pay attention to the height they reach)
5. Enter the Play Mode
6. Repeat step 4
7. Build and run the project (File > Build and Run)
8. Repeat step 4
Expected result: Particles behave the same way in all Modes
Actual result: The behavior of particles in Play Mode is different than in Edit Mode or Player
Reproducible with: 2021.3.25f1, 2022.3.1f1, 2023.1.0b19, 2023.2.0a16
Reproducible on: Windows 10
Notes: If the Particle System is not running in Edit Mode, then in the Particle Effect window (which appears after selecting the GameObject with Particle System), click on the “Play” button
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first