Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Strange enough, this NEVER happened when I play the Battle.Net version.
Could also be a bad memory leak somewhere that Blizzard did an oopsie. 99% of today's games have memory leaks somehow.
This game doesn't have the 13th gen "out of memory" errors that I know of like some of the newer UE5 games do. I just started playing this game a few days ago.
I have got 3 characters to level 20 "trial" limit without any issues though.
You can try to lower your Resolution down 1 notch and see if that helps for now. If you are using 4k, drop it down to 2560x1440p for example and test.
I'm sure it's a memory leak, but unfortunately it's only happening in the Steam version so far, during gaming sessions of about 3 hours, while I haven't experienced any crashes on the Battle.Net version. They definitely need to look into this.
raise your vram/pagefile to 16~32g
every newer games running dx12 or equivalent will require atleast 8~16g vram
+1