安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
But I'm having a problem. In the interest of letting some of our folks that don't own Contact in on the action, I ported the map over to Malden 2035 utilizing the basic instructions here (I have a lot of experience in porting and scripting A3), but for some reason the objectives are spawning at 0,0,0 about 95% of the time on our dedicated server.
What's weird is that utilizing the exact same mission file in a locally hosted server, there are no issues and the objectives spawn normally. Likewise, utilizing this default Livonia version of the scenario works just fine on our dedicated server. I'm at a loss as to where the issue could lie that would cause the objectives to ONLY spawn incorrectly on a dedicated server. Any advice?
The only compatibility issue I have seen is with Bloodlust.