(edited by jbuss.8469)
Showing Posts For jbuss.8469:
While we weren’t able to fix this issue for the March update, we’re still working on it. Thank you for your patience!
Thanks for at least acknowledging that the issue is still being worked on. Maybe next month, I guess
I (and several others) have the same issue. There’s another thread about it here in which an ANET employee responded that they are looking into what caused the issue 11 days ago. No further developments yet, but hopefully it will be fixed in the patch this month.