Search Issue Tracker
Fixed
Fixed in 2021.3.13f1, 2022.2.0b15, 2023.1.0a17
Unknown (hidden) 2022.1.X
Votes
1
Found in
2021.3.9f1
2022.1.16f1
2022.2.0b7
2023.1.0a9
Issue ID
UUM-14581
Regression
Yes
GetTriggerParticles returns 0 every few frames when getting a number of particles inside
How to reproduce:
1. Open the user’s attached project
2. Open the “SampleScene” Scene (Assets > SampleScene)
3. Select the “Particle System” GameObject
4. Enter Play Mode, and in the Inspector window, observe the “Particle Count”
Expected result: “Particle Count” doesn’t get set to 0
Actual result: “Particle Count” gets set to 0
Reproducible with: 2021.2.0a17, 2021.3.9f1, 2022.1.16f1, 2022.2.0b7, 2023.1.0a9
Not reproducible with: 2020.3.39f1, 2021.2.0a16
Reproduced on: macOS 12.4 (Intel)
Comments (3)
-
Bromm
Nov 11, 2022 21:47
Hooray! :)
-
Bromm
Sep 14, 2022 09:54
Also, this happened only when the number of particles in the Trigger was relatively high.
-
Bromm
Sep 14, 2022 09:50
It says "OF PARTICLES INSIDE", but I also faced problems with particles enter/exit. Some particles didn't get registered.
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2023.1.0a17):
Fixed in: 2023.1.0a17
Resolution Note (fix version 2022.2.0b15):
Fixed in: 2022.2.0b15
Resolution Note (fix version 2021.3.13f1):
Fixed in: 2021.3.13f1