Search Issue Tracker
Fixed in 2018.3
Fixed in 2019.1
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
-
richardkettlewell
Feb 08, 2019 16:24
Oh yes you're right I think it's out, as https://unity3d.com/unity/whats-new/2018.3.5 is also now live!
Look at that beautiful release notes entry...
"Particles: Fixed particle systems causing graphical glitches and error messages. (1099125, 1116662)"
-
pfSRT
Feb 08, 2019 16:10
Excellent, thanks Richard.
FYI, I just got an update notification for 2018.3.5f1 on my last launch of the Unity Editor, but the Unity Hub isn't displaying in Official Releases yet. In any case, downloading the update now from https://unity3d.com/get-unity/update -
richardkettlewell
Feb 08, 2019 14:15
I think we're hoping to get it out today. There was a problem with the patch (caused by my fix) which required a small follow-up fix, which has delayed things a bit...
Hope to have you all creating lots of particles again real soon..!
(We actually have a large number of smaller particle fixes coming in 2018.3.6 too, so we should be in really good shape when that patch comes out next week!)
-
bigfoott
Feb 07, 2019 16:58
It's been fun :) Hopefully 2018.3.5 releases soon.
-
pfSRT
Feb 07, 2019 15:41
Holding our breath for 2018.3.5f1 here. * GAAAASP *.......
-
KospY
Feb 07, 2019 15:07
The production ready release of 2018.3 is so close, hype!
As Raithza said, it was such a community here, my favorite page to check every day :D -
PatrickVRNerds
Feb 07, 2019 12:05
@RAITHZA Bro I feel you! Much success for your project. Hope we won't see each other in another issuetracker thread again. :D
-
raithza
Feb 05, 2019 14:19
To everyone who's been refreshing this page every day waiting for the fix in eagerness, I'm going to miss you. It really felt like we had some kind of community here. Good luck and godspeed, and may your games be memory leak free and filled with particles.
-
richardkettlewell
Feb 05, 2019 11:57
@JULIAN-MOSCHUERING, yes, that's a mistake. The fix is in that version, and should not be mentioned in the known issues. I've asked our release team to remove it from the known issues list. thanks for letting us know!
-
julian-moschuering
Feb 05, 2019 11:21
Listed in fixes as well as known issues of 2019.1.0b2. I guess the known issues entry is a mistake and now obsolete?
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
- VFX Graph not retaining reference to custom spawner
- Call Stacks - Calls to/Calls From - Temporarily revert to None upon Play Mode starting
- [URP] Blend Style panel is translucent and appears to be of different colour
- ProjectFilesGenerator.ProjectFileGeneration event isn't raised
- [Asset Import] Errors thrown on creating a project using microgame templates
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.