Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.48f1
2021.3.25f1
2022.2.20f1
2023.1.0b16
2023.2.0a15
Issue ID
UUM-35746
Regression
No
ArgumentOutOfRangeException is thrown when calling SetTriggerParticles overloaded method with offset parameter set to 0 and count parameter set to particleSystem.particleCount
Reproduction steps:
1. Open the attached “Repro.zip” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console
Expected result: No errors are present in the Console
Actual result: “ArgumentOutOfRangeException: offset+count should be smaller than the size of the particles list.” Error is thrown in the Console
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.20f1, 2023.1.0b16, 2023.2.0a15
Reproducible on: Windows 10 Pro (22H2)
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.