Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.3
Issue ID
BUR-1967
Regression
No
NullReferenceException is thrown upon entering Play mode when "3D Start Size" is disabled in Particle System properties
How to reproduce:
1. Open the attached “Particle Burst Test” project
2. Enter Play mode
3. Observe the Console
Expected result: No errors appear
Actual result: NullReferenceExceptions spam the Console
Reproducible with: 1.7.0 (2020.3.37f1), 1.7.3 (2021.3.8f1, 2022.1.12f1, 2022.2.0b4, 2023.1.0a5)
Reproducible on: Windows 10
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
This is not a Burst issue. I've attached a native debugger and caught the crash, and it looks like the x and y buffers in ParticleSystemNativeArray3 for particles.sizes are only set when "3D Start Size" is checked for that particle system. So it's probably expected behaviour, but if it's not, you'd need to contact the particle system team about it.