安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題






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.