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
-
FoxAlphaX
Feb 05, 2019 00:32
Unity 2019.1.0b2 releases
-
SuppleTeets
Feb 04, 2019 16:55
Thanks for the feex!
-
bigfoott
Feb 03, 2019 01:49
@SUPERJAYMAN it really shouldn't be that hard to read his post...
The fix made it into two versions of unity: 2019.1.0b2 and 2018.3.5, and neither version is out yet.
You will be able to download these versions when they release.
No need to be so rude
-
superjayman
Feb 03, 2019 00:54
@RICHARDKETTLEWELL
Again, right at the top it says 'Fixed in Unity 2018.3' So, where can I download the Fix? Your answer is convoluted and does not make sense, First you say it's fixed then quote...'should be available approx 1st February. 2018.3 testing is still underway.'..
-
SeanAtHandsome
Feb 01, 2019 14:22
Another quick vote of thanks to @RICHARDKETTLEWELL for keeping the lines of communication open. You do credit to Unity, and we certainly appreciate your diligence keeping us updated once the problem was identified.
-
chatrat12
Jan 31, 2019 17:50
Hear*
-
chatrat12
Jan 31, 2019 17:50
Huzzah! Glad to here the great particle drought of 2018/2019 is to finally be over :D
-
pfSRT
Jan 31, 2019 15:39
Excellent news! Many thanks again, Richard for keeping us updated on this! Please keep it up in future!
-
richardkettlewell
Jan 31, 2019 10:51
And another update - the fix has passed testing for 2018.3.5 and will definitely be in that patch.
Upgrade to that patch when it is released to get the fix. (hurrah!)Thanks again for everyone's patience and understanding while we fixed this horrible bug.
The tentative release date for the patch is 6th February, though it might end up coming out a day or so later, depending on how smoothly our release cycle goes.
-
richardkettlewell
Jan 31, 2019 09:40
Another update for everyone: The fix has now successfully landed in 2019.1.0b2, which should be available approx 1st February. 2018.3 testing is still underway.
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.