Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
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.