Инсталирайте 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)
Украински (Українська)
Докладване на проблем с превода
Just to be sure, if I build the instagib source I should be able to find the instagib game modes in the View-> World Properties, right? It's only showing the normal Chivalry game types for me.
Another weird thing: when the sdk was first released I made a mod with some custom weapons and made a dummy map with a reference to a custom weapon in a "Change Pawn Loadout" kismet node (to be able to cook it).
Now after rebuilding the scripts, I can't find the custom weapons in Kismet anymore, but when I open the old map the node with the reference is there . It doesn't recognize the other custom weapons or gametypes of the mod, only the weapon that was refereced originally. When I remove the script from the contentSDK folder it gives me external reference errors when I open the map.
You might have to also compile non-final release scripts, i.e. run "UDKEditor.exe make -full". That would also update Script/Manifest.txt; I'll have to update the Frontend tool to compile both ways.
copy Manifest.txt from UDKGame\ScriptFinalRelease into UDKGame\Script, overwriting the Manifest.txt in there. The editor uses Manifest.txt to find script classes it can use.