Multiplayer - Desyncs, disconnects & crashes

[Myzzrym]

Desynchronizations

In rare cases (at least we hope they're rare!), you might run into a desynchronization - which is what happens when the different players start seeing different things even though everyone is still connected to the game. For example, one player may see that their ally just missed their attack - while another see that they hit that same attack. Or that someone is chilling in front of the merchant, while the actual player is already 50 feet away opening a door.

When this happens, the host needs to make a save file and load it. There is no need to leave the session, the host can load the save file while the game is still going on.

If you have a high spec computer, please also check the following thread: https://steamcommunity.com/app/1096530/discussions/0/5737031847503078807/

Crashes / Disconnects

If a player suddenly crashes or gets disconnected, one of the remaining player (usually the host if they were not the one who crashed) simply needs to make a save file and then have everyone leave the session. Create a new multiplayer session by loading the file, and wait for everyone to join the lobby before continuing your adventure.

Other issues

As Solasta was not originally intended for Multiplayer (it's was created as a Single Player game), we had to use external services such as Proton to make it work. This unfortunately means that any issue you run into with Proton servers is unfortunately out of our hands - but we have noticed that those can sometimes be bypassed by switching regions or - in the worst case - waiting a few hours or days.

Note

- Using mods may cause additional risks of Desyncs

[IAce]

The crashes are still a problem and stopped my group from playing it.

[Brian]

Dec 10. We could not make a game. Photon server sucks.

[Lerrasien]

Desynchronizations are still a massive issue. My friend and I get them several times every time we play together. I'm curious as to how this is still an issue almost an entire year after this was posted...

[Alyss Madagain]

Logging in to this to say that the disconnects and crashing issues are still happening as well. It happens at least 3 times a game for me and my SO. He hosts and I join and we're both hardlined into the internet with perfect speeds so it's not the connection there.

[Malhagor]

same, crash as soon as the green dragon fly ... :s

[RayRay Jackson]

My buddy and I could never get through the 1st chapter because of this bug. The worst part is that when it happens in combat "in between" turns. You realize it happens, but can't make a save, or re-load without it happening again. It corrupts the save causing you to restart the campaign.

Shame, because it's a good singleplayer game.

[LaughingRamen]

Have you considered instead of using servers for matchmaking letting the end user run a dedicated private server instead?

[Samiri]

desynchronization has returned again. We played the very first fight and got it twice before we even ended the fight.

27-05-2023
And now again, it happend.

[Fasox]

I lost internet connection while I was loading a save file, the game crashed.
Since then I cannot play anymore, It even crashes when loading a savefile in singleplayer or starting a new campaign.

I tried to verify the files and reinstall the game, nothing changed.

[Price]

After Palace of Ice patch - 1.5.92, I've been getting mutliplayer desyncs constantly, huge differences being seen almost every time. This occurred along with the Unfinished Business mod on version 1.5.92.0. Currently, the Unfinished Business mod at the time of me typing this is now on version 1.5.92.1 and this desync issue is still occurring, please fix! Everything has been good up until this latest official update.

UPDATE: Desync seems to have been fixed after Unfinished Business mod patch 1.5.92.3 and me setting the FPS cap at 60 using the Nvidia control panel GPU settings for Solasta specifically.

[Prostheus]

Thought after not playing for a while with my friend that desync would be resolved, or at least less, but it's gotten worse. I've got a 2060 and my friend has a 3090. Tried the 60 FPS cap as well, no luck.

My game freezes, or just desyncs the actual actions. My friend can see my cursor when it's supposedly my turn, but my interface doesn't update, and no damage is done to enemies even though my friend's actions have caused damage.

[Prostheus]

After looking further into network related matters, I noticed I had mapped network drives of computers my system couldn't reach. I removed the unreachable drives (which I don't use anymore anyway) and it resolved the freezing!

[Haemol]

My group very often runs into item duplication issue after a desync. It should be easy to dedupe items based on some id. Such items cause a lot of issues, especially if an item is attuned it often then takes two attunement slots... so they cause quite a nuisance.

[Slapz Jiggleman]

My friend and I have been playing for a couple months.. Proton kicks me or him almost on an hourly basis... that is not acceptable for a $30 game that says its multiplayer.. if you cant run your own multiplayer servers then maybe don't even bother with multiplayer..its not worth it at all. we have to restart our session like 5 times a day and at this point i would get refund if could.. but Steam's refund policy is just a trash as Proton..

[tragicironing]

Originally posted by ShatDemon:

My friend and I have been playing for a couple months.. Proton kicks me or him almost on an hourly basis... that is not acceptable for a $30 game that says its multiplayer.. if you cant run your own multiplayer servers then maybe don't even bother with multiplayer..its not worth it at all. we have to restart our session like 5 times a day and at this point i would get refund if could.. but Steam's refund policy is just a trash as Proton..

Just picked up this game through the Steam sale earlier in December and am having these same issues when trying to play with a friend after the game worked with no problems for the first few hours. None of the reviews I read mentioned these multiplayer issues, unfortunately.