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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
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.