安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
1 Is almost finished, another one is currently in work and the third TTT-Map is still in planning.
Here is why I believe this map is better performance wise.
1. Unlike NPC-Metro / Town, this Map uses prop_static's and only a few prop_dynamics. Prop_static are the cheapest way (Performance wise) to add a 3d Model to a Map. On NPC-Town I ONLY used prop_dynamic & prop_physics, which dulls the Performance.
2. Open Areas are a nightmare to Optimize, if you can do it at all. On NPC-Prison this isn't much of a problem, since the outside is kept small and without many props.
3. I actually got better at using Areaportals. Thanks to a Map-maker buddy, I now know the jank of the Sourceengine. Areaportals determin what should be rendered and what shouldn't. These are the "Optimization-Essential".
4. I believe the lighting on NPC-Metro is an Issue. Every single lightbulb has a point_spotlight entity, creating a fancy lighting effect. But I overused it here.
5. Mapsize... NPC-Metro is huge compared to this Map.
Unfortunatly you cannot decide which NPC's should be able to mount turrets and shouldn't.
Because I don't use CS:S or other Textures in Hammer, so knowing what & where the Issue is woud help.
Can't check this myself since I don't have CS or other games Mounted.