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
No promises but you might be able to find a middle ground that runs well and is still playable.
Edit: "Render Scale" that's the slider. if you set that to 5% it looks like you're screen is 80x64 pixels or some super low equivalent. That's too low of course but maybe at 25%-50% you could still see the action...
Turns out, the problem was that I have my game capture set to keep the last 2 minutes of gameplay and , while this was always fine before, after the Ashlands update it was too much to handle. As soon as I shut off the auto-record the problem stopped.
Edit: I guess my point is... the game as a whole is more taxing on your system since the update.
Intel UHD 770 cant run this game so yours wont be able to unless you're okay with 50% res scale at 1080p and low settings and a ~30 fps experience and the game looks worse than minecraft.