Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem






https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3536876367&searchtext=gm_sanatorium_v3
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3323196875
Whenever possible Alex, try and optimize it as best you can. :)
For reference, I have a Core i7 9750H (6-core/12-thread overclocked to 4.5GHz), RTX 2060 6GB GPU, 16GB of DDR4 RAM, and run the game on a WD Black 1TB PCI-e SSD (efficiently hitting 3.5GB/s read and write speed) which loads up the toughest maps in 5 seconds. I am going to have to agree with the community that this is an optimization issue.
For the record: I've played on maps much bigger and more detailed than this one with little issue. If my frames tank, it's more of a sign that there's some form of optimization issue than anything.