Apparently you are not reading. This has been ongoing since Patch 2.0.5 for myself. Prior to that I had no issues what so ever. Not even during Early access. SE recognized the issue associated with Patch 2.0.5 on the Facebook Page.