安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Also (and I'm pointing this out because of the title of your thread), Hammer is completely unrelated to the Source engine. Hammer sucks. It always has and frankly, it always will; if it were changed enough to not suck, it would be so different that you couldn't call it Hammer anymore (I say this as a person who has been using Hammer on and off for over 10 years, so it's not that I'm unfamiliar with the program).
VRAD still compiles lighting into the bsp.
After much mucking about (a new VPK format, who knew?) I've managed to look directly at the water materials. They have $reflectonlymarkedentities enabled, which means that you'll have to enable the "Render in Fast Reflections" property of dynamic entities before they will show up.
http://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=96353222
Edit: you could also customise the material to disable $reflectonlymarkedentities...if you can extract it!
Edit: now you can extract it! https://developer.valvesoftware.com/wiki/VPK_File_Format/vpk2_reader.py