Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2019.1.X

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 SDK

-

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

Log in to vote on this issue

Comments (145)

  1. james_unity988

    Jan 13, 2019 21:11

    This bug is taking a serious toll on our project development. We are a small indie team and this kind of major bug really harms our opinion of Unity as our game engine of choice. We waited until after the beta to avoid this kind of issue, and there's no workaround. Please, please fix this bug ASAP!!

  2. FenyceAssets

    Jan 13, 2019 16:46

    Hope this get fixed soon, very annoying bug

  3. apesoup

    Jan 12, 2019 06:50

    issue persists in 2018.3.1f1 :-( - it's just not immediately apparent. I really hope this gets fixed soon because I'm afraid that the other option - converting back to unity 2018.2 - would involve a lot of work because of the new prefab system.

  4. unity_LzBuY34i8W2htg

    Jan 11, 2019 23:34

    Yeah never mind my comment below. The issue came back to me. It wasn't for a while but now I see it again. Guess it's typical memory leak issue often not happening in the beginning...

  5. chatrat12

    Jan 11, 2019 22:58

    Would be great to hear what work is being done on the issue and the challenges it's presenting. The current lack of communication on this makes it seem like it's low priority, even if it isn't. Last we heard, 'a developer' was looking into it. That kind of sounds like a 3rd party although 'developer' could refer to an employee.

    Can we get confirmation that it's actively being worked on?

  6. bigfoott

    Jan 11, 2019 22:42

    It's still an issue for me on 2018.3.1f1

  7. unity_LzBuY34i8W2htg

    Jan 11, 2019 18:02

    I just tried 2018.3.1f1 (came out yesterday 1/10) and it seems the issue is fixed!!!

  8. apesoup

    Jan 11, 2019 10:58

    Would it be possible to know if it is likely that this bug is going to be fixed within the next week or so? Otherwise I would start moving back to unity 2018.2 ?(although i really liked to new prefab system ...)

  9. apesoup

    Jan 11, 2019 10:58

    Would it be possible to know if it is likely that this bug is going to be fixed within the next week or so? Otherwise I would start moving back to unity 2018.2 ?(although i really liked to new prefab system ...)

  10. apesoup

    Jan 11, 2019 09:57

    Are the guys at Unity aware that this bug currently makes it virtually impossible to ship any VR game?
    Almost all games will use particle effects of some kind and this bug seriously worsens the experience because sooner or later the user will experience framerate drops that totally destroy the immersion.

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.

Latest issues

See all new issues