Alright. The issue should be fixed in 1.05.4, but we will investigate on our end and fix it for the upcoming 1.05.5 patch. Thank you for the information.
If you have further issues after 1.05.5 rolls out (which should be within the next week or so), let us know and we will begin to probe further.