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
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
-
jonagill_rr
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!
-
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.
-
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.
-
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.
-
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.
-
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.
-
wagaga
Jan 27, 2019 08:12
Any update?!!
-
wagaga
Jan 27, 2019 08:11
Hi Unity, when you could release a new version to kill this Bug?
Even if let us first normal use let the game to the player experience, the game died, our team died, this must not be what you want to see! -
wagaga
Jan 27, 2019 00:41
Unity always crash,windows always crash,the build game always crash!!!!
-
axvm
Jan 26, 2019 14:39
over 3 month since bug was reported and still not fixed in latest release... Did unity hired managers from bethesda? this is critical bug what the heck you guys were doing for 3 months?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
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.