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
I did not evan own the dlc´s but it did download and install them today, files auto verified by it self, and now it try to install the entire Game at 2% time remaining 1Year..
Steam is realy a pile of s*** !
I had set this virtual memory on my Games ssd but it was nearly full so maybe thats why it refused yesterday to start.
Indeed it is very bad vor ssd´s to allow win 10 use them as virtual memory device, but if not, most Games wont start.
Anyways, check your win 10 virtual memory option, wheather its on or off.
The error message specifcally states that it has run out of video memory. Is there a way to hard reset stored shaders to rebuild them?
/Edit: deleted config folder, issue still persists, game says that it has run out of video memory to allocate.
Given the fact that every single other game runs on my system and that Atomic Heart did as well prior to the last patch, I'd say devs botched something. :/
That's a very strange a rare problem. Please fill out bug-report form [forms.clickup.com], if you haven't already.
Also i can recommend you try to dissable Hardware GPU Scheduler.
Settings → System → Display → Graphics Settings → Turn "Hardware-accelerated GPU scheduling" to Off.
Hope that helps!
Hi there, thanks for the answer, but unfortunately this didn't help either. Submitted the bug report, hope you guys can figure out what the issue is.
The newest Nvidia driver GameReady 551.23 seems to cause this trouble and a lot of others by the way.
Reverting back to driver 528.02 seems to fix these issues and the BSODs I had.