Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción






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.