安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









This mission does look promising, I want to play around with it some to see if my group can get this working for what we have.
Performance wise, this was dragging my PC down to single digits at times with all the particle effects you were having run across the entire map, and the constant cluster shells you set to be fired at the airbase. Did this look impressive? Yes. Did it set a tense scene and tone? Yes. Is it worth making it nigh on unplayable especially if you are expecting players to not use a dedicated server (and thus, also headless clients) and run this on a self-hosted environment, meaning that we can't get performance boosts by allowing the mission server to handle the overall mission while headless clients take over the AI to spread the load out. CONT...
I'll be seeing what I can figure out about the whole shebang, and will update if I find that I had a PEBKAC error or some other solution presents itself.