2014-01-17, 08:07 PM
It's pretty pathetic that they haven't even acknowledged it in "Known Issues". Or the fact that this issue has been going on since June and still hasn't been resolved. I mean this thread basically has all the details of what causes the error, if I'm not mistaken someone even linked a GM to this thread. It just shows their dedication towards fixing it, I guess we will just have to hope more and more people get the error until they must fix it and cannot put it off any longer.