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









You need to make sure that the string that the paint mapping system check for is fully isolated, so for example, for the painted chrome, which in your mod have the addon data string :
accessory_addon_date : paint_ch.freightliner.cascadia2024.bumper
To make it work with the paintjob, you would have to modify it as the following
accessory_addon_data : paint.ch.freightliner.cascadia2024.bumper
The dot fully isolated the "paint" part of the addon data, which permit it to be recognized as something that fit the "bumper.paint" string for the paintjobs accessory files.
You would need to also adjust the suitable_for lines in other files, but that would fix the paintjob issue fully
Also, for the paintjobs, I might have a solution, need to test, but basically, from what I remember when I played with this, the files in the accessory subfolder for the paintjobs definitions file list the accessories string in a partial manner, so it would be possible to simply to take a default part and add a suffix for the paint mapping to apply the same (for example, let say the part that you based an additional bumper on have "airdam.paint" in it's unit name, you could use name the new part "airdam.paint_a" and it would theorically work)
- compatible with 1.55
- many fixes and improvements