Установить 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.