Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
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.