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 (144)

  1. B685d264641e7596f7192496e2cb38f7?d=mm


    Feb 04, 2019 16:55

    Thanks for the feex!

  2. 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

  3. 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.'..

  4. 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.

  5. B181d45c4808017ecd804d852fa5472b?d=mm


    Jan 31, 2019 17:50


  6. B181d45c4808017ecd804d852fa5472b?d=mm


    Jan 31, 2019 17:50

    Huzzah! Glad to here the great particle drought of 2018/2019 is to finally be over :D

  7. Ffa8f89534046843a34b50fead4aec99?d=mm


    Jan 31, 2019 15:39

    Excellent news! Many thanks again, Richard for keeping us updated on this! Please keep it up in future!

  8. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm


    Jan 31, 2019 10:51

    And another update - the fix has passed testing for 2018.3.5 and will definitely be in that patch.
    Upgrade to that patch when it is released to get the fix. (hurrah!)

    Thanks again for everyone's patience and understanding while we fixed this horrible bug.

    The tentative release date for the patch is 6th February, though it might end up coming out a day or so later, depending on how smoothly our release cycle goes.

  9. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm


    Jan 31, 2019 09:40

    Another update for everyone: The fix has now successfully landed in 2019.1.0b2, which should be available approx 1st February. 2018.3 testing is still underway.

  10. 52d039d5d5d7f28dbed71c033e247774?d=mm


    Jan 31, 2019 06:00

    So, where can I download the fix for 2018.3.0f2 ?

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.