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

  1. C2751a1fb854b1107025ef9499a3254d?d=mm

    Eyevi

    Apr 10, 2020 15:18

    Still have this error with a trailRenderer in Unity 2019.3.8f1 using universal pipeline...

  2. 6582a317622996669df3f619e3c60919?d=mm

    Shadowphax

    Apr 06, 2020 23:23

    Getting this in version 2020.1.0b4.3439

  3. 1143c6ede1698fadfc41a900aa456242?d=mm

    Gaspedal

    Mar 29, 2020 00:16

    Still not fixed. I get this error with Unity 2019.3.5f1 too

    Assertion failed on expression: 'task.rasterData.vertexBuffer == NULL'
    UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

  4. B633402633756f15926d3cd650dd6155?d=mm

    cubeeey

    Mar 22, 2020 16:36

    if you still get this error try to go under project settings < script execution order and set the script that you last wrote /that you think might causes the issue in there after default time and set it to 100 ... i think it has something to do with unity calling a script earlier than the others and this is causing an issue

  5. 93c499d24d364dfe7fe407a498d012b4?d=mm

    Steven-1

    Mar 21, 2020 11:02

    I have updated my project from 2018.3 to 2019.3, and since then I have this issue.

  6. Bc49078d5c0962682d1777978101701e?d=mm

    quick1brahim

    Apr 08, 2019 03:16

    This is 5000% better after the update. My memory consumption went from 10.3GB in the profiler (for a single particle system) to 200MB after update. Thanks!

  7. B685d264641e7596f7192496e2cb38f7?d=mm

    SuppleTeets

    Feb 11, 2019 23:26

    Rejoice!

  8. 3747c31b3b679fbfaf1d157286bfa431?d=mm

    bigfoott

    Feb 08, 2019 20:40

    Sweet, thanks again @RICHARDKETTLEWELL

  9. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm

    richardkettlewell

    Feb 08, 2019 16:24

    Oh yes you're right I think it's out, as https://unity3d.com/unity/whats-new/2018.3.5 is also now live!

    Look at that beautiful release notes entry...

    "Particles: Fixed particle systems causing graphical glitches and error messages. (1099125, 1116662)"

  10. Ffa8f89534046843a34b50fead4aec99?d=mm

    pfSRT

    Feb 08, 2019 16:10

    Excellent, thanks Richard.
    FYI, I just got an update notification for 2018.3.5f1 on my last launch of the Unity Editor, but the Unity Hub isn't displaying in Official Releases yet. In any case, downloading the update now from https://unity3d.com/get-unity/update

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.