GAME CRASHED 🎮

[(MS-22) ٭MELNIK٭]

Dear developers, please pay attention to departures from Orcs must die 2 for windows 10/11 users. On your site, the support does not work and you have to write here. Please pay attention to the discussions in the steam!!!

The game is knocked out in co-op mode. It can be knocked out in the middle or at the end of the match. It just crashes alternately, then from me, then from a friend. The problem was also noticed on Windows 7-8. But, on new versions, the game either does not install for some users, or crashes like mine. Please correct these errors.

[Wolf_Hastenichgesehn]

Unfortunately, these co-op crashes have been an issue for ten years, and because of more recent O.S. it has only gotten worse what had already been a huge annoyance to begin with, right from the launch of this game. It is very unfortunate, because apart from that, this game is basically flawless. Termy and me just made it way past wave 40, we would have made it easily past wave 50, gaining him multiple achievements at once - and then a crash occured and destroyed all that progress at once. *shrugs*. This is nothing the developers will (or maybe be even can) ever fix. Unless you are willing to take a huge risk of a crash occuring at some point, best abstain from co-op in endless mode - or suicide immediately after reaching your achievement goal.

[Wolf_Hastenichgesehn]

Interesting thread on co-op issues under Win 11:

https://steamcommunity.com/app/201790/discussions/0/3087772148450919599/?l=koreana

Oddly, there seems to be an issue that too GOOD an internet connection will cause the game to crash.


I have not tried the suggested solution yet, but ever since running Windows 11 (on a brand new, more powerful machine, to boot!), I have been encountering the following problem:


Going co-op in OMD! 2 invariably will heat up the machine like crazy, causing rapidly increasing lag, then crashing the game entirely (not just the connectivity, but the program itself).

Games that would overheat my old PC (which would run OMD! 2 just fine) run well (or at least better) now, so it can't be the machine, but must be some sort of software issue.