Hello, can you please make sure that the game itself and all of your drivers and software required for this game are up to date? If you are playing through Steam verifying the integrity of the game files might help. There is also a new patch for the game, so please update me if your problem is solved after the new patch, too.
I had same problem. What worked for me is I limit fps to 60 (in game settings) and I turned down graphics to Medium. Now I rarely crash like that.
There is some serious lack of optimisation, considering the game is "made for NVIDIA" and I run a 1080ti xD
FYI I am not overclocked.
Specs: 1080ti, 8700k, 16gb ram
I managed to fix this crash by limiting my FPS to 60 and dropping my graphics to Medium.
This game must be terribly optimised (and I have a 1080ti)!.
I ran furmark for 25-30 mins to check if my GPU was an issue -- it wasn't. Just bad optimisation.
Ok this is worse now. I can't even get past character creation/family section of the intro without crashing... same text dump:
This is just silly now! I have MORE than the needed specs, too: 1080ti, 8700k, 16gb... frustrating. My friend with a worse GPU is running it fine and its not even an NVIDIA xD
If you bought it on steam it takes 2 seconds to refund.
Anyways reading the error message it directly points at the GPU. First step I suggest is to verify game files in steam. Second is DDU and install your drivers on the latest version.
Can't play singleplayer cos crashing, can't play multiplayer cos crashing... Hmmm
Specs are 1080ti, i7 8700k, 16gb ram, installed on SSD
no overclocks etc
Am I able to refund at all? Pls advise as game is totally unplayable
Now my first problem was the fact I couldn't resume save games. While that is still a problem, I am ALSO receiving this error during both single player and multiplayer.
the game is now officially unplayable for me.
My specs:
1080ti
i7 8700K
16gb
bannerlord installed on SSD
No overclocks...
Hello, the developers are already informed about the corrupted save files issue, and we will inform you immediately when the issue is fixed. In the meantime, plase update me if the patch e1.0.0 has solved the problem.