Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2022.3.58f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99113
Regression
Yes
Particle System doesn't always play when ParticleSystem.Play() is called
Reproduction steps:
1. Open the attached “IN-94788 Particle Emission Bug - FAV.zip“ project (link in the internal comments)
2. Open the “Particles” scene
3. Go to the Game view (make sure the “Particle System” GameObject is not selected in the Hierarchy)
4. Enter Play mode
5. Observe the Game view
Expected result: The “Particle System” GameObject is emitting particles
Actual result: No particles are being emitted
Reproducible with: 2022.1.0a13, 2022.1.24f1, 2022.2.21f1, 2022.3.58f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Not reproducible with: 2021.3.49f1, 2022.1.0a12
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- The issue reproduces randomly about 50-70% of the time
- The issue reproduces the most often when entering Play mode while already being in the Game view, and the “Particle System” GameObject() is not selected in the Hierarchy
- Even though the Particle System is not emitting particles, ParticleSystem.isPlaying and ParticleSystem.isEmitting are returning “True”
- If the user moves from the Game view to the Scene view during Play mode, the “Particle System” starts emitting particles (sometimes, selecting any of the GameObjects in the Hierarchy or any of the assets in the Project window can also trigger particle emission)
- Reproducible in a new project
- Reproducible in the Player (reproduced 100% of the time during testing)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The tvOS platform appears in the Build Profile window even though it isn’t supported on Linux
- Error "IndexOutOfRangeException: Index was outside the bounds of the array" logged when selecting an Element in UI Builder with a specific setup
- "native code called abort()" is thrown in WebGL player when loading first scene
- Gradient Editor always opens on the main display when a multi-monitor setup is used and the Editor Window is on a secondary display
- Crash on core::base_hash_set when importing a specific package
Add comment