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
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.