Comments - KurdaBOy

After many tries, I managed to solve the problem. As with AMD graphics cards, I had to use "-nopbuffer" on the RTX2060S (because it looked like the shadows were taking up practically all memory). In addition, it was also necessary to use openGL from the mod folder and a partially edited "QeffectsGL.ini" file. I also had to force the use of a single CPU core (despite the fact that the game uses a single core anyway). If any of the steps are skipped, the problem returns. The above trick was only necessary for the RTX2060S card, when I mounted the old GTX1050Ti, nothing needed to be done. It looks a bit like a hardware compatibility issue causing the error in this particular case. It took me over half a month but it was worth it for this mod :D

I sent logs from a saved game, but the situation occurs regardless of whether I start a new game or load a saved game. It just takes more time before it crashes in a new game. I will do as you advise and try to run the mod from the original version if I still manage to buy it somewhere. This is a bit strange for me because I haven't had any problems so far and I've been playing since version 2.* or 3.*? Anyway thanks for all your help :)

Files updated. I'm trying to record gameplay but the game crashes faster than I can record it..

Settings and log files => Drive.google.com

Another strange thing i have steam version of the game but everytime i launch it with modded shortcut it opens Epic Games Website :D