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)
-
TenFiddy
Jan 26, 2019 13:54
Thank you for the work.
I decided to upgrade my unity version 2 weeks ago. I was using 2.17 and it was working well. This bug stopped my game cold. I was going nuts restoring old versions and piecing my game back together.
Thanks again.
-
superjayman
Jan 26, 2019 13:36
The fact that this is taking so long the Fix! is probably because it's a more fundamental bug then it sounds, this bug is a show stopper for developers, and quite frankly embarrassing to have in the first place. Is the fix you have working, please keep us updated. What do you mean by which version it will land in?? so you can't fix for all versions?
-
threeguysgamestudio
Jan 26, 2019 01:54
Would be great to get an official confirmation that you guys saw the comments indicating this bug does not only affect VR projects.
Would be a tragedy to fix it for VR and somehow not for the other cases =)
-
bigfoott
Jan 26, 2019 00:46
Glad to hear theres a potential fix. Fingers crossed!
-
SuppleTeets
Jan 25, 2019 18:19
I am also looking very much forward to the patch! :D :D :D! I sure would like to have particles in my VR project :D :D :D!
-
pfSRT
Jan 25, 2019 13:11
Many thanks for the update, Richard. We look forward to the patch!
-
richardkettlewell
Jan 25, 2019 11:38
Hey everyone,
We are currently testing a fix. I will post another update once we can say which versions the fix will most likely land in.
Free cookies for everyone once it's fixed (great idea Boco) ;-)
-
unity_KudLw9uurvth2A
Jan 24, 2019 09:31
same with 2018.3.2f1 version
-
boco
Jan 23, 2019 17:30
Thanks for the Update Richard. I think most people understand and I understand bugs and the like things happen. As long as we get some delicious cookies and maybe a backrub out of the dealio I think we can let it slide just this once XD. Nah keep up the good work I'm happy you guys are on it and I know it won't fix itself in a single day. Might be a week or three as things take time and ya'll have to make sure nothing else breaks with a fix.
-
boco
Jan 23, 2019 17:30
Thanks for the Update Richard. I think most people understand and I understand bugs and the like things happen. As long as we get some delicious cookies and maybe a backrub out of the dealio I think we can let it slide just this once XD. Nah keep up the good work I'm happy you guys are on it and I know it won't fix itself in a single day. Might be a week or three as things take time and ya'll have to make sure nothing else breaks with a fix.
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
- The Scrollbar becomes unusable when adding Elements to the List
- "One or more data file missing for baking set NewScene Baking Set. Cannot load shared data." error in Player when a specific project is built
- Choosing new HDR Colour using RGB values breaks colour on Intensity Selectors
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
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.