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
There are two workarounds and none of them involve buying the game twice.
Which did you apply? Be precise in describing what you did and do not leave a step out.
What i've tried so far:
- cleaning out both pc's profiles etc in the larian folder. (incl savegames, was just starting
zone anyway).
- used the 'trick' of changing the graphics + windowed mode
- Reinstalled the whole game on both pc's
- disabled the Larian Launcher (on both pc's)
Thx for the help ;)
And I meant you could save your money, as you can use a Steam feature to play together.
I am not pro Larian nor against, as I bought the game twice as well: on GOG.com and on Steam. Anyroads, I disgress^.
Your first approach is supposedly the correct one, by removing cache on both PCs. Normally that should work, but I am getting mixed reports, including yours.
There are two more approaches.
1.) Flush your network profile - on both PC - by starting the game twice and have the instances connect with each other. That would override any faulty network settings of the game.
How you do it:
Here you can find a manual how to find easily your game's folder with the executable to launch
https://steamcommunity.com/sharedfiles/filedetails/?id=3015842445
The very last approach goes like this
https://steamcommunity.com/sharedfiles/filedetails/?id=3020212758
That has a 100% success rate so far, as long as the router reset etc. happened before trying to get rid of any network cache. But it is only the last resort and the result is basically saying: something in the levelcache was not deleted properly - otherwise the result ought to be the same.
But it is a great way to control, whether it is something indeed with the cache or an entire other issue (network e.g.) we do not know about yet without checking that.
Let me know the results and good luck!