Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2017.3.0b7
Issue ID
970414
Regression
No
ParticlesStandardUnlit shader causes MissingReferenceException when Particle System StopAction is set to Destroy
How to reproduce:
1. Open Unity
2. Load tester-submitted project(Particles.zip)
3. Open '1.unity' scene
4. Select 'Particle System'
5. Expand material component.
6. Run the scene while observing material properties in Inspector(Repeat this step until issue occurs
Expected result: Particle System is destroyed without any issues and messages in Console
Actual result: Particle System is destroyed with some cosmetic MissingReferenceException errors being thrown in the Console
Notes:
* Reproduction probability varies between different machines.
* Typically reproduces within 10 attempts.
* The issue seems to be related to VertexStreams but altering Vertex Streams options in Particle System seems to not affect the problem.
Reproducible with - 2017.3.0f3, 2018.1.0a7
Could not test: 5.6.4p4, 2017.1.2p4, 2017.2.1p1, 2017.3.0a1('Particles/Standard Unlit' shader has not yet been introduced)
Verified in: 2018.2.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
- Complex Sub Graph connected to a Voronoi node is ignored when the shader gets applied as a Material
- Compute Shader property not set error when entering play mode with path tracing and PBR sky
- "WebGL Publish" detects WebGL module and allows building when it is installed without restarting the project
- Editor is non-responsive and flickers when multiple Water System instances are enabled
Add comment