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
Another possibility, because heap memory is not properly managed and prone to fragmentation, is that the memory has become too fragmented over time as they allocated and freed blocks of heap memory and the allocation of a large enough block failed.
Sounds like you used up all your vram.
Exactly the same error at exactly the same quest. Since I got it a bit before for the first time I think the error stems from the green Serpent outfit (which you can't exchange at this point for story reasons if you want to progress). Guess waiting for a patch is the solution...
Edit: I can always provoke it when I talk to Akna.
I can't speak for others but I have a souped up 1080 and have 8192 MB of dedicated video memory. I do run the game on ultra and may have to change that if I can't get it to work.
Well heap limits are generally accociated with memory, transient is generally accociated with variables, After doing a bit more research on the matter, it deffinitly has to do with memory (vram or system I don't know) however the Heap Limit may be exceeding the program rather than your actual hardware. Regardless it sounds like a memory leak of some sort, only it doesn't seem to be effecting everyone.... So its a rather strange case.
Generally Memory leaks effect everyone (and those with more hardware power to throw at it get effected last or least)
However this seems to be effecting people with decently good hardware.
So it may be external software, drivers, or a faulty installation causing this, which would make it harder to track.
For your next troubleshooting step try isolating the game. Turn off all other software in the backround and then try running it again. Then try installing it again. And as a final step, try a clean windows install (just install windows to another drive and duel boot). If even after all that the game still fails, then we are looking at a very specific hardware hiccup of some sort.
It may also be a particular order of operations done in the code that caused a loop to build but not release memory. If it requires a specific order of mission / game events to trigger, who knows.
I can provide my save game if needed for others to test/devs to debug.
Exact same spot here. 64 GB RAM, 1080 ti
Thats where I had the issue also, after 3-4 crashes and completing that quest, finished the rest of the game with no issues.