Larian Studios Forums Divinity - Original Sin Divinity - Original Sin - Technical Issues EE Bug : Game Crash to Desktop when Coop Rejoin

Hi,
We are facing a critical bug on Coop 2 Player Internet campaign. Our last 2 savegames are "dead". Let me explain the issue after laying down our configuration.

In our case we are in this configuration :
- Steam Host (Me) on Windows 10
- Steam Client (Pal) on Windows
- Version (Lastest version - 2.0.99.676)
- Game opened to Friends Only Rejoin

Whenever the client tries to load the game, it crashes at around 95%. Sound stops, loading stops and pops a crash window. The crash generates Crash Dumps, that I can provide along with the savegame.

For the moment, game is stuck can't continue to play.

What we tried :
- (A) I Load the save > Pal tries to rejoin > Crash.
- (B) I Load the save > Zone to EoT (Moving from crash area)> Pal tries to rejoin > Crash.
- (C) Clear game cache in MyDocuments\... > Same as A > Crash
- (D) Send savegame to pal > He does (A) > Crash from my game

We have played this game on this same campaign for some hours, and did face something quite similar once. We saved in combat and that exact save and further one were crashing. We had to use an older save to pursue.

This time we did a combat save on Act 1 Pirate Fight. Finished and were near Lair. Any save from then is unusable. (Coincidence ? Just emitting ideas)

I have zipped Savegames / Dumps. Anyway I can send those to support ?

We are stuck, and can't see why those save are lost. We have done quite some chunk of the game (All the Cave With Robot, Pirates after etc... on 1 save - We tend to avoid mass saving for the challenge) and are quite ... unhappy with the matter. Anyway to have this checked ?

Regards

Zyniel

Please email supportdos@larian.com, with a description of the problem and the report.zip file generated by the D:OS EE Analysis Tool (for Windows), for the host and client system
Extract the zip file somewhere and run the AnalysisTool.exe. When that loads, browse to the install folder (if it is not automatically detected), optionally run the tests first, and then generate a report (it will be saved in the same location as the Analysis Tool).

The reports will contain system and game information, as well as your saved games. To reduce the file size, the host can delete most of the saves from the zip, just leaving the two that crash and maybe the most recent working save, and the client can delete all saves.

You can add a couple CrashDump files to the report, or zip them together separately.