Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
I'm sorry that you've had an issue with multiplayer on Anno 1800.
To fix this issue, please make sure that both the game and Ubisoft Connect are updated to the latest version. Please also ask your friend to do the same.
Should the issue persists, please reach out to our support, mentioning the error code you received. You can find the link here[www.ubisoft.com]
Should you need more info, please do not hesitate to ask.
Thank you very much.
- Ubisoft Support
Actually before update 17 everything was fine
Have you tried to follow the steps in this article[www.ubisoft.com]?
If the issue still persist after this, feel free to come back !
In the meantime, if you have any other questions, feel free to ask and we will do our best to help you !
- Ubisoft Support
A lot of people have had issues since the latest update. Try hosting your multiplayer game while logged out of Ubisoft Connect and see if the issue persists. I believe Ubisoft's cloud saving feature is causing desyncs for a lot of players now.
When you start the game, uisoft connect itself asks you to log in to your account
You should only need to do that once to bind your accounts. Afterwards, Steam will automatically log into your Ubisoft Connect account on your behalf when you to launch the game. I feel this method eliminates whatever redundancies exist by launching the game through Steam with an existing login with the Ubisoft Connect client.
I can't pinpoint the exact cause, but I'm not the only one who eliminated their LR40 desync messages with this method. Others described logging out and back in manually as a solution. Regardless, the problem seems like it's coming from Ubisoft itself.
Do you mean putting your Ubisoft Connect launcher in offline mode, and then relaunching the game on Steam? (since you do need to be logged into an account when starting the game/need to log in with one when prompted, I assume you meant the online/offline toggle within the launcher settings).
It can certainly be something to try, although the game might require a connection in order to launch.
Tom Sawyer If you could please give the article linked by Ubi_Massilia a go, and let us know if your issue continues, I would appreciate it.
- Ubisoft Support
I appreciate the inquiry. I can only say my method is anecdotal at best, but I'll try to describe my experience to the best of my ability. I first encountered the LR-40 error message when prompted by the Ubisoft Connect client that I had been logged out due to inactivity. Since I typically don't maintain a login with the Ubisoft client, and because the client was citing issues with not being able to synchronize with the cloud, I happily obliged by logging in.
The very same day, every single game that I had attempted to host would immediately and repeatedly encounter LR-40 desync errors. My friends and I assumed it was due to a connection problem with a member of our group, as he was recently joining us, so he left to verify his game and even went so far as to reinstall it. In the interim, we played without him, and the LR-40 desync errors continued. After a while, I had to assume that something I did caused the LR-40 desync errors, and the only thing I could think of was that I had actually logged into Ubisoft Connect for once. So, I logged out. The LR-40 desync errors stopped completely.
As it turns out, Steam will use your Ubisoft account details when launching the game, so the Ubisoft client is a redundancy in this case. I believe the source of the LR-40 desyncs is due to a redundancy between the clients -- or perhaps because of the cloud saving feature itself.
It is worth mentioning that I have never launched Anno 1800 outside of the Steam client. Coincidentally, the LR-40 desyncs started and stopped by actively logging into and out of the Ubisoft Connect client. I have not tried to recreate the experience, but I could try.