安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Error: Object(6 : 5) not found
2019/09/25, 23:20:40 Server: Object 6:9 not found (message Type_459)
2019/09/25, 23:20:40 Server: Object 6:12 not found (message Type_92)
2019/09/25, 23:20:40 Server: Object 6:10 not found (message Type_120)
Error: Object(6 : not found
Error: Object(6 : 9) not found
Error: Object(6 : 12) not found
Error: Object(6 : 9) not found
Error: Object(6 : 12) not found
Error: Object(6 : 10) not found
this is the error in my unit's server RPT, is it possible that these error are the one causing desync?
Another one at [1465,3739,0], see https://imgur.com/sULkywU#
Pole on the road at [3078,4294,0], see https://imgur.com/c0LcfhL
One of the side of the road at [4803,2798,0] slightly warped, which i'm not sure is intended, see https://imgur.com/rWi2A4i
"khoramshahr\data\ot\podestab10m.p3d: house, config class missing"
When starting a mission or the editor with Khoramshahr and then doing the same in Uzbin Valley, there is a certain clutter in Uzbin Valley that is always black.
Culprit is the clutter configuration for MushroomsHorcak in this terrain. Uzbin Valley uses the same model a3\plants_f\clutter\c_thistle_Thorn_desert.p3d as clutter, but under a different clutter name. The difference is that Uzbin valley uses the swLighting=0 parameter for the clutter, while Khoramshar does not change the parameter and it seems that the default =1.
When adding swLighting=0 to the clutter in Khoramshahr, then the problem with black clutter does not happen in Uzbin Valley. When using swLighting=1 for the clutter, the problem appears also.
Slightly remember to see that also a while ago but apparently never reported it.