Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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!