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

    Jan 23, 2019 16:26

    We are still working on this issue right now as a priority.

    Posting comments in all caps won't make it happen any faster. We understand your frustration, apologies that it's still causing you all problems.

    Feel free to check back for updates, but please know that this page will be updated as soon as a fix is on the way.

    I also seem to be forced to use the comments rather than the Response field at the top, as that is broken for me too and won't let me edit it :-(

  2. pfSRT

    Jan 23, 2019 09:16

    Same issue here.

  3. superjayman

    Jan 23, 2019 02:06

    There's also an issue with your comment posting :) Posts multiple times for some reason

  4. superjayman

    Jan 23, 2019 01:57

    WHAT'S THE ETA STATUS ON THIS BUG.????? This is just not good enough! To have such a severe bug going unnoticed and unfixed by now!.. WHEN WILL YOU HAVE THE FIX????

  5. superjayman

    Jan 23, 2019 01:56

    WHAT'S THE ETA STATUS ON THIS BUG.????? This is just not good enough! To have such a severe bug going unnoticed and unfixed by now!.. WHEN WILL YOU HAVE THE FIX????

  6. superjayman

    Jan 23, 2019 01:55

    WHAT'S THE ETA STATUS ON THIS BUG.????? This is just not good enough! To have such a severe bug going unnoticed and unfixed by now!.. WHEN WILL YOU HAVE THE FIX????

  7. Hyperbolic_Games

    Jan 22, 2019 22:53

    Indeed this is a show stopper and not specific to VR as the OP title implies. I upgraded to 2018.3.2f1 and have this error spamming my console and killing my frame rate.

    How did this get past QA let alone be unresolved for so long? I really hope this gets fixed very soon.

  8. Hyperbolic_Games

    Jan 22, 2019 22:50

    Indeed this is a show stopper and not specific to VR as the OP title implies. I upgraded to 2018.3.2f1 and have this error spamming my console and killing my frame rate.

    How did this get past QA let alone be unresolved for so long? I really hope this gets fixed very soon.

  9. Hyperbolic_Games

    Jan 22, 2019 22:49

    Indeed this is a show stopper and not specific to VR as the OP title implies. I upgraded to 2018.3.2f1 and have this error spamming my console and killing my frame rate.

    How did this get past QA let alone be unresolved for so long? I really hope this gets fixed very soon.

  10. Hyperbolic_Games

    Jan 22, 2019 22:48

    Indeed this is a show stopper and not specific to VR as the OP title implies. I upgraded to 2018.3.2f1 and have this error spamming my console and killing my frame rate.

    How did this get past QA let alone be unresolved for so long? Can we have an ETA on a fix?

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