You might be right—I just remembered a thread from about a month ago here on the forums where someone was noticing the same thing. If this is referring to the same bug, then it appears to have been fixed in 5.1.
You might be right—I just remembered a thread from about a month ago here on the forums where someone was noticing the same thing. If this is referring to the same bug, then it appears to have been fixed in 5.1.