Have you tried reinstalling the game?

Have you tried removing the -malloc parameter?

Could you please explain what the problem is as I do not understand from your description.

Have you tried the troubleshooting page?

@dedmen thanks a lot!

Please Help, I have deleted some apps and may have stuffed up battle eye

Event handler is just a code you add that is executed upon an event. If you wrap your code in a function you can call this function separately from event. However if you are asking that execEventHandler will generate an event, this is not possible.

Optional param since 1.99.146475

up

Nvm, workshop item ID's

[
["CUP Units DEV Version r710 (r710-r710 UNITSSVN) (12|Jun|2020)","@[DEV] CUP Units",false,false,"GAME DIR","f3fb8a4c62443ac799c7c0e00f645b1f32cf1376","c96577b4","F:\Steam\SteamApps\common\Arma 3\!Workshop\@[DEV] CUP Units",0],
["CUP Weapons DEV Version r1486 (r1481-r1486 WEAPONSSVN) (12|Jun|2020)","@[DEV] CUP Weapons",false,false,"GAME DIR","6dbd7c052ce2ae68803e10f6a3653d0b046881d8","bb1c4965","F:\Steam\SteamApps\common\Arma 3\!Workshop\@[DEV] CUP Weapons",0],
["Community Base Addons v3.15.1","@CBA_A3",false,false,"GAME DIR","33eef5c0ed583d1222319460b184090513193287","131bbb64","F:\Steam\SteamApps\common\Arma 3\!Workshop\@CBA_A3",0],
["Arma 3 Contact (Platform)","enoch",true,true,"GAME DIR","a4ee0aa9675b9578de2c2742dfa75f14b463b311","2c003588","F:\Steam\SteamApps\common\Arma 3\enoch",1.02179e+006],
["Arma 3 Tanks","tank",true,true,"GAME DIR","f20f91e6d4de2f912c9aef10440b9f7cdd9186ba","ee2006c9","F:\Steam\SteamApps\common\Arma 3\tank",798390],
["Arma 3 Tac-Ops","tacops",true,true,"GAME DIR","e173f6dac22cbfba9a80f06ab6274f283a79ccf1","99fbe961","F:\Steam\SteamApps\common\Arma 3\tacops",744950],
["Arma 3 Laws of War","orange",true,true,"GAME DIR","483d1b17bba31a73aca3382baca90726e5fb3b27","85779468","F:\Steam\SteamApps\common\Arma 3\orange",571710],
["Arma 3 Malden","argo",true,true,"GAME DIR","f70c5909dd0cf7f85041d1a6f8117fcddbefbeb4","119b97f7","F:\Steam\SteamApps\common\Arma 3\argo",639600],
["Arma 3 Jets","jets",true,true,"GAME DIR","02935f9fd087965351eaf1af421fee2349cb46b7","a7400e7","F:\Steam\SteamApps\common\Arma 3\jets",601670],
["Arma 3 Apex","expansion",true,true,"GAME DIR","ae333819e353cbcf64d25c1a18b182e1c48de485","dd4515be","F:\Steam\SteamApps\common\Arma 3\expansion",395180],
["Arma 3 Marksmen","mark",true,true,"GAME DIR","31fcc6f8175f2f8ca204c30f0d70656f23349084","afb3a14a","F:\Steam\SteamApps\common\Arma 3\mark",332350],
["Arma 3 Helicopters","heli",true,true,"GAME DIR","ed81c94ee14b0d6bcc0c09947bec1d80ac81285a","fbdee859","F:\Steam\SteamApps\common\Arma 3\heli",304380],
["Arma 3 Karts","kart",true,true,"GAME DIR","57fdc8d27afb5ec5890666c22efaa27555c6a60c","be245321","F:\Steam\SteamApps\common\Arma 3\kart",288520],
["Arma 3 Zeus","curator",true,true,"GAME DIR","65c7e2c50ad25b4d727780b435533113ad1e9cf3","bb8e34f1","F:\Steam\SteamApps\common\Arma 3\curator",275700],
["Arma 3","A3",true,true,"GAME DIR","","","F:\Steam\SteamApps\common\Arma 3\A3",0]
]

The path and steamID at the end will not be possible tho. Paths could contain private info of the user, and I hoped the steamID would also be the workshop itemID of the thing... sad.

you have DLC data already
https://community.bistudio.com/wiki/getDLCs
https://community.bistudio.com/wiki/isDLCAvailable
I think these are sufficient for DLC

This was fixed in 2017 during Tanks DLC.
So you have a different issue @ElTyranos

Report file: https://drive.google.com/file/d/1-p-xtKumyT01CSwiHV2gTZw8bepNQ-4p/view?usp=sharing

merged task with https://feedback.bistudio.com/T147075

merged task with https://feedback.bistudio.com/T141408

Extending task to include all tracked amphibious vehicles

BTR, BRDM, OT64, and TPz1 have been addressed, swimming PX of Tracked vehicles will be handled in https://feedback.bistudio.com/T147075 as that's a different issue

Resolved in final 1.2, hot1 and 2 now has the proper range of 4000m

@dedmen
Sorry for the terribly late response, I simply forgot to reply!
Yes, the environmental one would be "global" for all envSounds but run locally on the player's machine only.

In T151813#2075027, @BIS_fnc_KK wrote:

Could you try to run your mission without any mods?

Could you try to run your mission without any mods?

I am the mission maker.

{F1824904}The "Open folder" / "Open folder in windows explorer" actions crash the launcher .

Can you please send us the specific mission?

Have you contacted the Mod makers as well?

No, I can't load loadouts with restricted items.
It would be nice if blocked items (arsenalRestrictedItems) were not accessible in the arsenal so that we could control the content.
Unfortunately, this can currently still be avoided under certain circumstances.

The fix is added in 1.99.146447 please test on or after

Are you able to load saved loadout with restricted items? arsenalRestrictedItems prevents user from loading saved loadouts that contain restricted items as per https://community.bistudio.com/wiki/Description.ext#arsenalRestrictedItems it does not disable items you have in inventory or in arsenal

Can you guys please assign this under "Dayz" tag, since this was opened by mistake for "Arma 3"

If anyone can help me out here please ?????

@Kremator - Hi. 0xC0000005_-_ACCESS_VIOLATION is a general error. It can be caused by hundreds of different things. So it is more than likely that your error is caused by something completely different than the one SoupVEVO reported. That is why every error has its separate report so that we can try to figure out what the problem is, it is likely that during certain errors the game itself is not at fault, it might be a mod, or a specific setting on your computer, or a certain update of the gpu drivers or even DirectX and a ton of other things as well.

fixed in 4788

To expand the purpose a bit: We want/have to replace the mod list in the main menu. The functionality is hardcoded, so we need a scripted replacement. Unfortunately currently this is not fully achievable. Hence the request.

[Feature request] Extend modParams with modDir info

https://feedback.bistudio.com/T151841

fixed for 1.2 release

Fixed in version 1.2.4773