2012-11-02, 05:44 PM
This is a return of a previous glitch that was supposedly fixed in the patch previous to this one i.e. my brother encountered the problem following the most recent patch (Halloween).
The original thread reporting the issue dates to the beginning of the month, it was reported to be fixed in the week I mentioned. My brother reencountered the glitch and a new complaint has been logged. You probably shouldn't expect expediency, but who knows, maybe it's the same glitch and they know how to fix it, but if they do, why hasn't it been fixed?
The original thread reporting the issue dates to the beginning of the month, it was reported to be fixed in the week I mentioned. My brother reencountered the glitch and a new complaint has been logged. You probably shouldn't expect expediency, but who knows, maybe it's the same glitch and they know how to fix it, but if they do, why hasn't it been fixed?