安装 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(越南语)
Українська(乌克兰语)
报告翻译问题










As for fire department, I am working on a generic red/white department livery. May get a Terrastar as well.
That's the reason why I made several hours beta testing, so that the colors are the ones I want to use. In case I need other effects or even bit different ones for other vehicles/props, I will give it a new name.
When I am making invisible props with several lightnings, I make a whole package.
I thought about doing something like this too but ended up with this thoughts:
1. Every time I want to edit one effect I've got to do so on all vehicles if the effects name is the same (conflicts due to the fact that the game loads probably just one effect with that name)
2. I don't know how exactly these effects are loaded so there might be an additional effect instance for every effect defined in worst case
To avoid both I'm working on some kind of a repository for my effects - I just upload the EffectsDefinition.xml and probably a ParticleEffectsDefinition.xml as a prop and list it as an dependency. So the only thing I include in the assets will be the VehicleEffectsDefinition.xml.
This works just fine and reduces risks like running into game limits and such stuff. Just to mention my thoughts ;)
Best wishes!