@nemot
I think BIS' logic (and I kind of agree here) is that the optics' BDC pairing would be self-evident given the weapons they are nominally paired with. For example, the RCO is meant for 6.5mm NATO as it's paired with the MX, the ARCO is meant for 6.5mm CSAT (and works with 5.8mm DBP out to 5-600m), the MRCO is meant for 5.56mm as its paired with the TRG and Mk 20, and the ERCO is meant for 5.56mm as well as it's paired with the SPAR. As far as I know, there isn't any specific 7.62mm pairing as all of those weapons are used with adjustable optics

Seems to be fixed in 1.62

Could you please download this version of Launcher, unpack it to your Desktop or Documents and run it from there? If that is the issue I've original though it was (when fixing Workshop cache), it would be fixed. It that is the issue with Windows 10, then it won't be.

Can you enter any of the mod folders in the G:\ArmA 3 Mods\!Workshop and for example open some file (e.g. readme) from there and some Addons folder in one if the mods? I came across an article about a bug in Windows 10 that would explain the errors in the log.

If I did it was not done intentionally.

Affected lamps:

May I ask you, did you ever manually modified or deleted mod from Steam Workshop cache?

So restoring the default legacy mods folder in the launcher to "C:\SteamLibrarySSD\steamapps\common\ArmA 3" fixes the issue with the corrupted mods. Doing the "Find in Folder" option does show the normal hidden "!Workshop" folder, "C:\SteamLibrarySSD\steamapps\common\ArmA 3\!Workshop".

So the current stat is, like it was before APEX Update.

The problem seems to be specifically with the "Guarded by..." trigger not creating a point to guard. I had the same problem and I fixed it with manually creating the guarded points using the "createGuardedPoint" command.

Thanks for the answer,
I don't use any mod, here's the crash report, as you can see by it's name, I didn't tuch it:

It's very irritating.

the value you are seeing in the weapons config is not exactly a weight of the weapon, it is a combination of weight and volume. Containers have the capacity set in the same unit (mass). Stamina and other units properties are of course set accordingly to take this into account.

At the request of a community member, adding prior establishment that the ability to do these directional lights is already in the engine.

Of course, any crash that happens during normal gameplay is worth reporting :)

Hello guys,

thank you for the logs your have provided.

I will upload any new crash dump if I'll encounter any other problem like this :)
Of course I think there are no repro steps since it happens randomly, but I think that any info about a possible crash are always useful to the devs. :)

Hello again,

Thank you for the feedback, however if there already is an ticket with the same report from you, rather update that one instead of creating a new one. It is then much easier to keep track of the issue.

a new update was released on Monday, would you mind checking that one out and get back to me whether this issue has been resolved?
After the update, we recommend to verifying integrity of the game cache via Steam.

thank you for the feedback.

Seems I did not attach the report file, as the size is over 1mb.

Hello.
We suspect the issue is caused by one of the servers, but we can't pinpoint the exact cause nor reproduce it with any public server we can reach.

Can you please re-upload the sample? Edit: disregard, found out u mean our own sample ;) (shame)

This should be closed.
It's a Windows bug, not Arma's.

Whoops. Already reported here.

Cool,
I hope you can find a solution. If you need anything else let me know.
Good luck :)

Yep, thank you :)

when you start the game provides "the executable file of the game could not be found. restore the game using steam client" check cache and nothing, I ask for help from experts

no it's me who thanks you for your help

thank you for the feedback.

при запуске игры выдает "исполняемый файл игры не найден. восстановите игру при помощи клиента steam" кеш проверял и ничего, прошу помощи у знатоков.

If it's not much trouble, please try to find out what the situation is when playing on different servers, perhaps the official ones or some other servers, preferably the ones that do not require mods.

Thank you,

Would you mind sending us fresh crashdumps please ?

Confirmed, would appreciate a params toggle to delete vehicle spawned when the garage is open. Currently, only way to remove the vehicle is by another script, ex. to run a local script (if in mp) to detect a vehicle at the spawn point and delete it. Messy and expensive.

Now that's it :) Thank you, we will look into them to see what might be wrong.

thank you for the feedback. Could you please create the report file (Launcher > Options > Prepare Arma 3 Troubleshooting report > Save report) and upload the ZIP file here?
Should you encounter any problems when uploading the file here, please upload it to some free file sharing service (e.g. Dropbox) and post the link here so I can check them out.

@Xeno, thanks for the heads up, should anything else come in mind, please let me know

@Jawsh Since Xeno is unable to reproduce the issue on his side, perhaps there're some corrupt or inconsistent files. What about game cache integrity?

here is the crash report{F37940}
here the log of the launcher

Hello,
sorry for the inconvenience, we'll fix that as soon as possible. In meanwhile, changing the legacy mod storage folder in mod options to a different drive (and then back) should fix the issue.

Hi Razazel,
Are these what you need? From the AppData/local/arma3 folder?

Hello,
this error is caused on the graphic card while rendering Launcher window. Please try to update your graphic card drivers. If that doesn't help, go to Options / Launcher Options and check "Disable Launcher's UI hardware acceleration".

Thank you for the crashdumps, will look into them immendiately.

Were you playing solo or in coop with other people? If you were playing coop, were you playing on official or unofficial servers or did you host the game on your machine?
Any piece of info you are able to remember and might seem relevant will help.

It's not the mission which is causing it because when I add drawingInMap = 0; to my server.cfg I can't draw lines on the map when running the mission. So map eventhandler was nothing more than a guess :)

Maybe caused by adding a draw eventhandler to the map?

I have encountered the same problem in 1.62.

Two of the custom mission files I can reproduce this issue on are: co40 Domination! Blufor (co40_domination_3_45_blufor.tanoa) by Xeno and GunGame-Tanoa by OPTiX.

I double checked my server.cfg settings and the startup parameters in the BAT file. They are definitely correct, but players can still draw lines on the map.

Well, i tested it further and now its even tasks built in editor using the modules. SO yea my game is broken and i have no idea why... :(

So did more testing on the latest DEV build as of today. I tried the following and still same affect:

I have also attempted to use the server browser on another internet connection as to avoid issues associated to firewalls but even on a separate network, the same servers are still not visible in the server browser.
An example of a server that is not visible in the server browser: 149.202.31.21:2302
An example of a server that is visible in the server browser: 192.223.29.245:2312