Search Issue Tracker

Fixed in 2018.3

Fixed in 2019.1

Votes

224

Found in

2018.3.0b8

2018.3.0b9

2018.3.0b10

2019.1.0a9

Issue ID

1099125

Regression

Yes

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

XR

-

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

notes:
- 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 (146)

  1. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    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.

  2. 52d039d5d5d7f28dbed71c033e247774?d=mm

    superjayman

    Jan 31, 2019 06:00

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

  3. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    Jan 30, 2019 22:49

    ADNARO, yes this issue is probably the same problem you are seeing.

  4. 09fc8d8421bfb6caf76af5ab75979db2?d=mm

    Adnaro

    Jan 30, 2019 15:27

    Hi guys, just wondering if my issue fits into this category and upcoming fix or whether I should be looking elsewhere.

    I'm running a bunch of particle effects in VR and seem to have huge memory usage (~35GB) when entering playmode for the *second time after opening Unity* (first playmode attempt is really smooth).

    Profiler shows XR.WaitForGPU at ~150ms and under Memory, I'm getting the majority being taken up by GfxDriver.

  5. Ffa8f89534046843a34b50fead4aec99?d=mm

    pfSRT

    Jan 30, 2019 10:09

    Many thanks for the updates and now the fix! We very much look forward to the release.

  6. Eedf8eed6015e1c3ed12c75bad501b17?d=mm

    apesoup

    Jan 30, 2019 07:20

    Finally!! The game felt soo empty without particles :-) - But how do we get the free cookies?

  7. E567259fc57a48aaffae92dd2ae60eed?d=mm

    wagaga

    Jan 30, 2019 01:55

    Good!!!!!!!Thanks unity, my game will hot!

  8. 0d143caf525f20fa64a84c3ff32dcd70?d=mm

    tblank555

    Jan 29, 2019 20:07

    Richard, thanks for the quick and clear response. You guys are awesome.

  9. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    Jan 29, 2019 19:13

    TBLANK555, the vertexBuffer error you have seen is part of the same problem and the fix covers it too.

  10. 0d143caf525f20fa64a84c3ff32dcd70?d=mm

    tblank555

    Jan 29, 2019 19:05

    After upgrading my project to Unity 2018.3.3f1, I see this error spammed at runtime, but I also see this error spammed, which no one seems to have mentioned here:

    task.rasterData.vertexBuffer == NULL

    (Note: vertexBuffer, not indexBuffer)

    Is this error related to this bug? Does anyone else see the vertexBuffer error along with the indexBuffer errors?

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.