WTF is happening. Yesterday and todays updates both caused complete settings reset in the client. Including window size, position, etc.
This happens because someone decided its a good joke to change settings filenames. Yesterday client was reading settings.yaml, today its settings.yml, which name will it be tomorrow?
Also stop asking for UAC elevation multiple times during update. One should be enough. Uplay PC was asking twice. Ubi Connect is asking thrice. Next rebranding will cause it to ask 5 or 10 times?
I cannot agree with the sentiment enough. Also, why does Ubisoft Connect require 3 UAC allowances for each update?
Basically, every update I have to not just relog-in and then resize the window to not be miniscule at 1440p, rechange where I have my Uplay games locations (because they're on my E drive), undo that I don't want your post game notifications (because they always have been and always will be annoying), redo my download speed limit, turn off in-game notifications, and unselect allowing strangers to send me game invites. And lately, that's been every other day. Not to mention the store within the client is unbearably laggy.
I have every client known to man yet I don't have one more annoying than Uplay.
I knew I couldn't be the only one with this issue. The other day I went to play a game and it launched from Steam, but switched to UC, which is normal but it acted like I didn't own the game. I had played the same game less than 24 hours earlier. I exited out of UC and restarted it to an update that had no idea who I was and my settings were wiped. Now come to about 15 hours later to start a game directly from UC to have a sudden update where again my settings were reset but at least I did not have to login again. Restarted UC just to be safe that kept my settings.
And yes the 3 UAC has been around for years and really <bleeeeep> annoying. This is the only program I can think of that does this for an update.
Hello,
Please accept our apologies for the frustration caused by having your settings reset. For the sake of clarifying the situation, we released a hot-fix on July 14th, which was rolled back on July 15th due to an unrelated issue. This issue was addressed and the hot-fixes were re-deployed on July 20th. I've asked for further information from the team why this happened, if it can be avoided in future, or least could be foreseen ahead of time. Once again, we apologize for the inconvenience caused.
Thanks.