安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
獎勵
Decompiling and recompiling a map creates a clusterfuck of errors that need to be addressed, because like in this scenario its probably a bunch of brushfaces clipping in to each other because of a bad decompile that makes the vis fubared.
Check the map for errors in radiant before you compile, then check it manually for things that need to be fixed.
Make sure that you dont have any errors during compilation(Mainly thinking about VIS.), do not to use skyboxes, use areaportals on doors, use hint brushes if your vis doesnt split up the areas well enough during compilation.
Props on the design though, looks great overall.. but its insanely bad optimized, which might seem like it doesnt matter much with todays computer.. but you have to consider that this also means that the server will always send information about everything on the map to all the players all the time(Known to cause crashes.).
it is not the issue here, LOL
I am using r_vertexLight "0" (drops from 250fps to 160)
with r_vertexLight "1" small drops, but ppl with weak PCs will have a problem even with stable 125fps