安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
[::RegisterParticle#176132] :: [WARNING] :: Duplicate particle filename: iddle_exhaust; GetParticleIDByName will only work with the first path if there are two different paths.
Function: 'RegisterParticle#176132'
Stack trace:
scripts/3_Game/particles\particlelist.c:305
BaseBuildingPlus/scripts/3_Game/bbp_config.c:149
Function: 'RegisterParticle#176132'
Stack trace:
scripts/3_Game/particles\particlelist.c:305
BaseBuildingPlus/scripts/3_Game/bbp_config.c:149
EC2AMAZ-R4RR2LJ, 29.11 2021 20:05:07
NULL pointer to instance
Function: '#InitGlobals'
Stack trace:
BaseBuildingPlus/scripts/4_World/items\t3_foundation\bbp_t3_foundation.c:36
Duplicate particle filename: iddle_exhaust; GetParticleIDByName will only work with the first path if there are two different paths.
Cid Vicious the #InitGlobals error means you are running too many mods, you have reached the DayZ Script limit, nothing can fix #InitGlobals but removing mods to clear up script space. DayZ can only run so many mod scripts before that error pops up.