Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
I saw a suggestion in another thread that the game may use SSE4 or AVX instructions that older processors do not have, causing a crash. I don't know if this is truly the problem but it would explain why I managed to run it on a newer system but not my main computer. However, a commenter on the first page said they have an i7 12700F which is fairly new and should support AVX2, so maybe this is not really the issue.
I have an i7 860 myself, which is fairly old, if I go to Steam > Help > System Information it shows AVX as unsupported. Despite being an older CPU it has no problems running a great deal of newer 3D software, so I'm not used to having problems with Steam games like this, but it's possible Animal Well doesn't have fallbacks for CPUs without these instructions.
It could be something else entirely, though. I'm just mentioning it because it was one of the comments made elsewhere. All I could gather from the various threads are that some minority of users are consistently having this issue. Not sure at all what kind of hardware each may be running, though, as few people mention it.
(My own GPU is also relatively old, a 750 Ti, but like with the CPU I am not used to this being a source of compatibility problems. It's very rare I can't get something to run, though I might turn the graphics settings down on some games to get a better framerate.)
The devs are definitely aware of the issue, though I don't think they've posted here. There are comments acknowledging it in the company's discord (but no explanation or resolution yet, that I have been able to find).