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
Comments (145)
-
richardkettlewell
Jan 30, 2019 22:49
ADNARO, yes this issue is probably the same problem you are seeing.
-
Adnaro
Jan 30, 2019 15:27
Hi guys, just wondering if my issue fits into this category and upcoming fix or whether I should be looking elsewhere.
I'm running a bunch of particle effects in VR and seem to have huge memory usage (~35GB) when entering playmode for the *second time after opening Unity* (first playmode attempt is really smooth).
Profiler shows XR.WaitForGPU at ~150ms and under Memory, I'm getting the majority being taken up by GfxDriver.
-
pfSRT
Jan 30, 2019 10:09
Many thanks for the updates and now the fix! We very much look forward to the release.
-
apesoup
Jan 30, 2019 07:20
Finally!! The game felt soo empty without particles :-) - But how do we get the free cookies?
-
wagaga
Jan 30, 2019 01:55
Good!!!!!!!Thanks unity, my game will hot!
-
tblank555
Jan 29, 2019 20:07
Richard, thanks for the quick and clear response. You guys are awesome.
-
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.
-
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?
-
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!
-
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!
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.