Search Issue Tracker

Fixed in 2018.3

Fixed in 2019.1



Found in





Issue ID




[VR] Particle Systems cause "task.rasterData.indexBuffer == NULL" error and lead to graphical glitches



Steps to reproduce:
1. Create a new project
2. Enable VR
3. Create a particle system
4. Enter playmode and put it in your HMDs view
5. If error doesn't show, repeat Stop / Play of playmode again. (when doing this i can repro it with the MockHMD)

Result: "task.rasterData.indexBuffer == NULL" error in the console and potential graphical glitches

Reproduced on 2018.3.0b8, 2018.3.0b10, 2019.1.0a9
Not reproduced on 2018.2.16f1, 2018.3.0a1, 2018.3.0b7
Regression introduced in 2018.3.0b8

- Is known to also cause memory leaks

  1. Response avatar

    Resolution Note (fix version 2018.3):

    The fix has now landed in our various release versions. 2019.2.0a4, 2019.1.0b2 (available approx 1st February), 2018.3.5f1 (available approx 6th February). Thank you for your patience.

Comments (139)

  1. F08983fcdf45e87ec3c3fd74ab302450?d=mm


    Feb 05, 2019 14:19

    To everyone who's been refreshing this page every day waiting for the fix in eagerness, I'm going to miss you. It really felt like we had some kind of community here. Good luck and godspeed, and may your games be memory leak free and filled with particles.

  2. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm


    Feb 05, 2019 11:57

    @JULIAN-MOSCHUERING, yes, that's a mistake. The fix is in that version, and should not be mentioned in the known issues. I've asked our release team to remove it from the known issues list. thanks for letting us know!

  3. 503834d37736f47cd539abd411df3a5e?d=mm


    Feb 05, 2019 11:21

    Listed in fixes as well as known issues of 2019.1.0b2. I guess the known issues entry is a mistake and now obsolete?

  4. 72290f700e36465de5b0fd9b43a1ea05?d=mm


    Feb 05, 2019 01:15

    Unity 2019.1.0b2 the problem whit particle error fixed

  5. 72290f700e36465de5b0fd9b43a1ea05?d=mm


    Feb 05, 2019 00:32

    Unity 2019.1.0b2 releases

  6. B685d264641e7596f7192496e2cb38f7?d=mm


    Feb 04, 2019 16:55

    Thanks for the feex!

  7. 3747c31b3b679fbfaf1d157286bfa431?d=mm


    Feb 03, 2019 01:49

    @SUPERJAYMAN it really shouldn't be that hard to read his post...

    The fix made it into two versions of unity: 2019.1.0b2 and 2018.3.5, and neither version is out yet.

    You will be able to download these versions when they release.

    No need to be so rude

  8. 52d039d5d5d7f28dbed71c033e247774?d=mm


    Feb 03, 2019 00:54


    Again, right at the top it says 'Fixed in Unity 2018.3' So, where can I download the Fix? Your answer is convoluted and does not make sense, First you say it's fixed then quote...'should be available approx 1st February. 2018.3 testing is still underway.'..

  9. 3ad1c400c7b187f94a6cd3b20e938c00?d=mm


    Feb 01, 2019 14:22

    Another quick vote of thanks to @RICHARDKETTLEWELL for keeping the lines of communication open. You do credit to Unity, and we certainly appreciate your diligence keeping us updated once the problem was identified.

  10. B181d45c4808017ecd804d852fa5472b?d=mm


    Jan 31, 2019 17:50


Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.