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

  1. 0d143caf525f20fa64a84c3ff32dcd70?d=mm

    tblank555

    Jan 29, 2019 20:07

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

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

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

  4. 88765fbdd8eb13c1ddd4ba212f41a165?d=mm

    unity_LzBuY34i8W2htg

    Jan 29, 2019 18:10

    Glad this is finally fixed. Thanks for the hero developer fixed this issue behind of the scene and hope the people involved on this matter have peace in mind now. Looking forward to the update!

  5. 4103a22c52b0d724829bb03fa307b56b?d=mm

    jonagill_ag

    Jan 29, 2019 17:55

    Thank you for the consistent updates, @RichardKettlewell! We really appreciate them, since this bug is affecting our ability to develop and patch our live game. Please let us know if the fix does fail final testing and the release date slips so we can plan accordingly.

    Thanks again!

  6. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    Jan 29, 2019 17:07

    Hi again.

    The fix has now landed in our mainline code, which is the first step towards getting it out in a patch to you all.

    These are the following versions it should be fixed in:

    - 2019.2.0a4
    - 2019.1.0b3
    - 2018.3.5 (release date approximately 6th February)

    For 2019.1 and 2018.3, we will only hit these versions if it passes final testing in those versions. We will find that out in the coming days.

    Thank you for your patience.

  7. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    Jan 28, 2019 09:49

    >Would be great to get an official confirmation that you guys saw the comments indicating this bug does not only affect VR projects.

    Yep, we know it's not only VR and the fix should cover all cases.

    >What do you mean by which version it will land in?? so you can't fix for all versions?

    It will be fixed in 2018.3 and above. I mean the precise patch version is not yet known as it is still in testing.

  8. 3747c31b3b679fbfaf1d157286bfa431?d=mm

    bigfoott

    Jan 27, 2019 21:52

    The reason there's no mention of this bug in patch notes is because the bug hasn't been fixed yet, it's not that hard of a concept to understand. A dev replied 2 days ago saying they were testing a possible fix and would update us once ready.

  9. 85f86a16c477dca3280a348adaf8d591?d=mm

    dimitris_baud

    Jan 27, 2019 20:36

    2018.3.3 was released two days ago, no mention of this bug in the release notes... This issue has by far the most votes (by a factor of x4), I wonder what process is in place that prioritizes other issues. Dear technical director, please pay attention to your users.

    https://unity3d.com/unity/whats-new/2018.3.3

  10. 22b8a0e4907a3bf944ed142796d106de?d=mm

    HAIRGROW

    Jan 27, 2019 20:36

    I was just about to finish upgrading my project when I discovered this bug with the Particle Systems. I can confirm that this bug is present in Unity 2018.3.0f2 as it is listed as an official build, in Unity Hub, but not listed as one of the test builds being used to reproduce and track this problem. I'm working on a VR project using SteamVR. Originally I was using Unity 2017.4.1f1 but was forced to upgrade to keep up with SteamVR 2.0. Unfortunately, Unity 2018.3.0f2 is the only build that works correctly with it. I make heavy use of Particle Systems, so I hate to find this out just now. If I had known, I would've waited before upgrading.

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.