Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
112
Found in
2018.4.18f1
2019.3.0b12
2019.3.0f6
2020.1
2020.2
Issue ID
1226357
Regression
Yes
'task.rasterData.vertexBuffer == NULL' errors when using a Particle System
Steps to reproduce:
1. Open User-attached project
2. Run the Sample scene
3. Tab out and wait for at least 3 minutes
Expected: nothing appears in the console
Actual: errors appear in the console
Reproduced in: 2018.4.18f1, 2019.3.0b12, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Not reproduced in: 2019.2.21f1, 2019.3.0b11
Notes: Inconsistent reproduction, versions may not be entirely accurate, the bug may appear sooner than 2019.3.0f5, but I have not been able to reproduce it there
RichardK updated notes: Improved first affected versions based on additional information from QA/community
-
Resolution Note (fix version 2020.2):
Fixed versions:
2020.2.0a8
2020.1.0b8
2019.3.14f1
2018.4.23f1
-
Wavefaring
Apr 16, 2020 02:51
ICANFLY342's steps are slightly off, in my testing. You shouldn't need to turn on "Cast Shadows", and the two systems only need to be visible in the Game window. If they are not in view of the camera, you can go look at them in scene view and not get the error.
I can reproduce this error with the following steps:
Create New Project
1. Add a Particle System to the scene on any object.
2. Add a LineRenderer to the scene on any object.
Note: They can be on their own separate objects, or on the same object, it doesn't matter.
3. Both Particle System and LineRenderer must be in the view of the Camera.
4. Error appears almost immediately after hitting play, and repeats over and over.This bug can be reproduced in every 2018.4 version starting from 2018.4.18f1.
And it can be reproduced in every 2019.3 version starting from 2019.3.0b12.For those looking to avoid this error:
Unity 2018.4.17f1 is the last 2018.4 version where this doesn't happen.
And Unity 2019.3.0b11 is the last 2019.3 version where this doesn't happen. -
DayatXIII
Apr 15, 2020 14:09
Mine happens with the trail renderer, I'm using Unity 2019.3.9f1
-
Farresto
Apr 15, 2020 07:34
Looks like this bug had already happened and was supposedly fixed: https://issuetracker.unity3d.com/issues/vr-particle-systems-cause-task-dot-rasterdata-dot-indexbuffer-equals-equals-null-error-and-lead-to-graphical-glitches
-
Farresto
Apr 15, 2020 07:28
I'm having the issue after updating to 2019.3.9f1, so it looks like it's still happening.
-
skaughtx0r
Apr 11, 2020 04:36
I just updated to 2018.4.20f1 and am getting this error, seems to be caused by Particle Systems.
-
sincerelysleepy
Apr 10, 2020 17:47
Also getting this with line renderer in 2019.3.0f6
-
Eyevi
Apr 10, 2020 15:24
Got this in 2019.3.8f1
-
icanfly342
Apr 09, 2020 18:42
I can reproduce this bug in all the 2019.3.x versions that I have:
Create New Project
- Add a Particle System, goto Renderer-Tab and turn on "Cast Shadows"
- Add a LineRenderer to the scene
- Both Particle System and LineRenderer must be visible in either Game or Scene window!
- Press Play, wait a few seconds... the error should show up -
CobiTwoDesperados
Apr 01, 2020 17:36
I use a particle system and a trail renderer. Started to get this error out of the blue. 2019.3.1f1
-
ismaxx
Apr 01, 2020 13:21
in my case, have a lot of line renderers without problem, appears only with particles
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
richardkettlewell
May 07, 2020
Fixed versions:
2020.2.0a8
2020.1.0b8
2019.3.14f1
2018.4.23f1