Larian Studios Forums Divinity - Original Sin Divinity - Original Sin - General Coop bug - character walks off map

When my friend and I play a game of coop multiplayer, within the first 3 minutes, his character will just take off and walk off the map. He will walk through mountains, over rivers, through all features until he hits something that will kill him ( i.e lava).

To him ( i am the host) he sees his character freeze in place, then suddenly die. All the while, he is able to see my characters movements.

when this occurs, the ingame chat no longer works between us either. But he can watch and see what i am doing.

Sounds likea connection error? Anyone have any fixing ideas

My friend and I are experiencing the exact same thing. We are extremely unhappy about this as we experienced it during beta and hoped it would be fixed by now.

EDIT: this only seems to affect non-host players. but it affects them immediately and makes the game completely unplayable.

Please email supportdos@larian.com, with a description of the problem and the report.zip file generated by the D:OS support tool (for the PC version), from both systems. This will include network information, which should hopefully help Larian identify the problem.
The report file also contains your saves, which are presumably not relevant to this problem, so most can be deleted to reduce the file size.

You may know this, but I'm fairly sure that is lag and it is synching too slowly.

While i'm willing to admit that it *could* be lag, it seems odd that it is only happening in this game. We can host other games totally fine, we both have extremely beefy rigs and good connections to the internet...no dropped packets, pings of less than 45 between each other. Also, with lag, you'd expect some slight delays, not a connected client to see a monster or host wander completely off screen for the next several minutes.

Also, when a connected client views a monster wander off, the host can still attack it, but the client has no idea where that monster is now. so it completely screws the rest of that encounter.

Finally, if the client sees the host wander off, the host will essentially walk in a straight line across the map, triggering any events and clearing the map.

Again, it's not that the 'lag' is temporary. when 'it' (whatever it is) happens, it stays.

Finally, I'm curious to know if you'd try a coop game? If not, you should so that you can experience how game-breaking this is.

By beefy I mean:
Win7 64bit
16Gb RAM
i7-3770 3.5GHz
AMD 7950

This is happening to me as well.

I noticed the issue shows up when I try and have my character pick up something (e.g. A shell off the beach at the beginning of the game)

Please fix!

I experienced this in single player.

What happened was I was getting ready to fight the Baron, and Character A was in a dialogue where it was obvious that clicking "(End.)" would initiate the fight, so I ordered Character B to cast a summon as a kind of pre-buff, then quickly switched back to Character A and clicked end. Character A then ran straight through walls, cliffs, etc, right into the water and across the sea, which was really funny because the battle continued anyway and the Baron's minions killed my other main character in the first round. I laughed my ass off at the hyperbolic cowardice, then loaded (luckily, I saved right before the fight).

I think it has something to do with command simultaneity, which would explain why it happens more often in coop, and only happens in single player when you're attempting hijinks.

Has this been fixed at all yet? I've been getting the exact same issue, along with a new issue where it takes several seconds for me to move around inventory items on occasions, along with repeated disconnections. I'm using comodo firewall (which always seems to be the problem) but have disabled it for now and I've also opened 2 ports supposedly needed for D:OS. Is there anything else I can do to fix these issues? Does anybody else have experience with using comodo while playing this game or other games? Please note I'm posting this as a D:OS issue not a Comodo issue as this doesn't always happen.