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
-
apesoup
Jan 11, 2019 09:56
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. -
bigfoott
Jan 11, 2019 08:04
Really hope this gets fixed soon.
-
bigfoott
Jan 11, 2019 08:01
Really hope this gets fixed soon.
-
BlindMystics-P3TE
Jan 10, 2019 03:48
+1 Happens on 2018.3.0f2 ... Started happening after upgrading from 2018.3.0b6
Notes:
> Only happens when using a HMD. If running without a HMD it doesn't occur.
> Doesn't happen the first time I press play after opening Unity, but will happen every time after the first time.
> Seems to be also causing memory leeks. It will sometimes stop climbing by it's self, also seems to stop climbing if you pause the game, sometimes it doesn't stop climbing and my PC runs out of memory and shuts down immediately. The only way I've found to get back the runaway memory is to restart Unity.
> Looking at the Unity profiler the memory leeks appears within the GfxDriver (I've seen this up to 26.27 GB!) -
kavanavak
Jan 10, 2019 01:06
.. still an issue i see :/
-
ErThu
Jan 09, 2019 21:41
Another issue that I found is that after exiting play mode, the whole scene view is lagging extremely hard. Profiler shows around 100ms per frame for Gfx.WaitForPresent(). When I exit play mode without using VR (using the VR Rig simulator from VRTK) I do not have this issue and the error TASK.RASTERDATA.INDEXBUFFER == NULL does not occur.
-
nbhagatx098771
Jan 08, 2019 23:55
Yeah getting the same issue. First, I thought its SteamVr but now I can see its Unity 2018.3.0 with the particle system
-
chatrat12
Jan 08, 2019 05:19
Any status on a fix? Is it still being investigated or has the underlying issue been found? Is a fix underway?
-
RPowers
Jan 08, 2019 03:16
Does anyone know how, if possible, to downgrade to Unity 2018.2? It crashes every time I try.
-
Gothwaite
Jan 08, 2019 01:06
+1. As soon as I upgraded to 2018.3.0f2 my particle systems that worked fine started spitting out this error.
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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.