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










from the DRO mission menu, on the information tab, click "reset to defaults". usually the problem is unusual or unexpected ACE settings that DRO cannot work with.
that is unlikely to be my mission. Access Violation is typically when the Arma 3 program is trying to read or write to memory it does not have permission to read or write to, such as memory for a different program, or bad memory that isn't responsive. this can be many things, since it's referring to virtual memory space, which can be physical memory or disk space. in some extreme cases, addons that heavily modify the game can do this, however this mission does not do anything special like that with preprocessing or non standard includes.
https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit#0xC0000005_-_ACCESS_VIOLATION
that's more of a faction config issue in whatever faction mod is in use, where that faction uses a script or something to modify a default loadout based on CSAT or NATO. if you have some specific examples i can test for those though.