Overlord II

Overlord II

Screen goes black after a few loading screens
So huh, yeah. I'm playing Overlord and my screen goes entirely black and the game is unresponsive after the loading screens with Gnarl. It happens after a few minutes of playing. I've changed to compability mode with Windows XP and Vista but it still happens. Anyone know a fix?
< >
Showing 1-12 of 12 comments
For anyone who cares, It seems disabling Steam Overlay did the trick. Also set compability mode for Vista Service Pack 2, just in case.
ThefredLittle Mar 25, 2024 @ 5:08am 
Originally posted by Journalists Aren't People:
For anyone who cares, It seems disabling Steam Overlay did the trick. Also set compability mode for Vista Service Pack 2, just in case.
Sorry to ask this is probably stupid but I have windows 10 I'm having a very similar issue after I smash the man with the statue in nordberge I go to the town hall then it just goes black. Idk how or if I can change my compatability can you help maybe?
ThefredLittle Mar 25, 2024 @ 6:15pm 
So I figured out how to do the compatability change it's still not working so confused
Sorry bud, never had that happen so I have no idea what could fix it... Maybe reinstall or check integrity first
Surim Apr 13, 2024 @ 5:23pm 
I also got this error, has anyone solved it?
Nerrad Jun 6, 2024 @ 10:55am 
i also have this when going into the minion lair everytime.
eisbaer05 Jul 26, 2024 @ 4:43am 
is there any solution for this "crash-problem" ??
N1nj4 Aug 31, 2024 @ 7:08pm 
I'm having the same issue, steam refused to refund because I've tried so many different fixes I've ran over 2 hours on the game.
N1nj4 Aug 31, 2024 @ 7:09pm 
Originally posted by Journalists Aren't People:
For anyone who cares, It seems disabling Steam Overlay did the trick. Also set compability mode for Vista Service Pack 2, just in case.
I tried this and no luck... Any other ideas?
Tayno Dernul Nov 9, 2024 @ 8:32am 
Originally posted by N1nj4:
Originally posted by Journalists Aren't People:
For anyone who cares, It seems disabling Steam Overlay did the trick. Also set compability mode for Vista Service Pack 2, just in case.
I tried this and no luck... Any other ideas?
Привет бро у меня такая же ошибка исправил я ее тем что снизил качество графики на минимум и запустил в окне после этого обратно все вернул и вроде все окей
Iron Knights Dec 12, 2024 @ 2:07am 
Windows XP SP3 is the failsafe of compatibility for old games, if not Win 7.
Never do Vista, no dev. programmed for that wreck of an OS.
Turn on OpenGL for this game in GPU Profiles. Add the executable to the profiles if not found in the list.
Hrath Apr 7 @ 12:55am 
Now I've ran into this issue as well, and I think I've found a solution after some testing.

For those who just want a quick fix, I've found that just turning off "Depth of Field" fixes it.

Now for those who want more details, I've initially tried most of the things already suggested by others(disable steam overlay, disable fullscreen optimizations, compatibility mode, and run as administrator), but nothing ever worked. However I stumbled upon the suggestion to set the config utility's video settings to medium. Which did in fact work. Which got me thinking, if using a different preset works, then surely it must be one of the settings. so I did the following to isolate the culprit:

1. I set the utility to custom, and disabled all the checkboxes, but set all the drop menus and sliders to max.
2. I decided upon a route to follow, in order to test the effects of each change in settings.(I settled upon the following route: Tower, Nordberg, Tower, Burrows, Tower, Forge. And repeat that at least twice over)
3. After each successful run enable half of the checkboxes that were still disabled(This way I don't have to do 10 runs, and can half the number of offending candidates with each run, narrowing it down much faster.)
4. Repeat 2 and 3 until the issue pops back up(Which it did at of course the very last checkbox "Depth of Field". So glad I didn't go one at a time)
5. Revert all prior solutions to make sure it was just this one setting(Turns out it was).

Now full disclosure, I also DID try the GPU profile, but due to some issue with NVIDIA, which is unrelated to this, that didn't work out I'll try to sort that one out later, but I don't expect it to make too big of a difference.

So now I'm successfully running it at max settings sans "Depth of Field".

Hope that helps.
< >
Showing 1-12 of 12 comments
Per page: 1530 50