I see in the folder in path from you only .rtp's. No .mdmp and .rtp

Seems to be the case also for :
13:46:49 Warning Message: No entry 'bin\config.bin/CfgMagazines.US85_38x_M151'.

I looked through your report log however i can only see .rtp's in there with no unusual exits.
Can you check Windows: C:\Users\<Name>\AppData\Local\Arma 3\ for your most recent .mdmp and .rtp and add them to the ticket?

The notes in the previous comment still apply in CSLA 1.1.

These antennas behave more sensibly in CSLA 1.1.

In CSLA 1.1, a new retexture of the Vest was added which has a believable armour rating. However, the original Vest (now Vest (M81)) still apparently offers no armour. The other vests mentioned here still have incorrect armour ratings too.

This was fixed in CSLA 1.1.

These nonfunctional attributes are no longer present in CSLA 1.1.

In CSLA 1.1, the MAAWS and SMAAW now use an appropriate reload animation.

Since CSLA 1.1, the VG-70 no longer accepts 40mm ammo and has its own 26.5mm ammo. It did not gain magwell compatibility with GM 26.5mm ammo; I leave it to the devs to confirm whether that counts as a full fix or not.

In CSLA 1.1, flares were added for UH-60s, but not the Mi-17.
After close inspection, I believe the Mi-17's flare launcher is a small module located on the port rear door. Since the rear doors can open, moving the flare launcher, I suppose there may be engine limitations preventing this from being made functional...

This critical issue was resolved in CSLA 1.1.

This was fixed by CSLA 1.1.

Confirmed fixed in CSLA 1.1.

Verified fixed in CSLA 1.1.

Yes, technical support advised me all this. None of this helped.

thank you very much for fixing this, this was really problematic in using the asset

Hello, haveyou tried the steps mentioned here?
https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit#0xC0000005_-_ACCESS_VIOLATION

Hello try verifying your files through stream
or deleting the file you mentioned then verifying.

Seems this was already fixed

Agreed, this would be extremely useful for a number of projects I'm working on too

Ehh you didnt actually post the crashreport.
Please click and drag the file in here, you can even do it in a comment i believe

Hello can you provide us with your crashfiles? Most importantly the .RPT and .MDMP of the session with the crash.
https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

In T167985#2375063, @Tenshi wrote:

Your issues seem to be caused by "futurecept", not by Arma 3

We do not have a fix for it yet, sorry.

1

i am having the same problem how can i get this fixed?

This does seem to be fixed on live currently, this ticket can be closed

Hello sorry to hear about the problem.
This is a known issue with the Texture cache.

Thanks! The problem was the MSVC c++ 2013 redistributable x64 not being there. Thank you so much for your help!

Your issues seem to be caused by "futurecept", not by Arma 3

Hello,
Have you tried verifying your files via steam?
If that doesn't work can you see if the issue also occurs with BattlEye disabled?
It could also be that the MSVC c++ 2013 redistributable x64 is not installed (but steam should install that automatically)

Well lets say i do, how would i change that?

What is your PC username, does it have "special" non-ASCII letters in it?

Hello,
Do you have an RPT and MDMP of the crash so we can look into it?

I have the same issue. and so far I have found at least 4 extra questions with the same issue on the forum. All left unanswered, 2 of them claimed by @dedmen.
https://feedback.bistudio.com/T150598
https://feedback.bistudio.com/T148574

The workaround is to delete and re-create the UAV's crew, you can then use it till next landing. Very annoying, hope it'll be fixed someday.

EascapeFromTarkov's report is still there. The workaround is to delete and re-create the UAV's crew, you can then use it till next landing.

FYI issue still exists, it seems like once the savegame is bigger than a certain uknown treshold no "continue.Arma3Save" is generated and unless you rename any existing save to the "continue" one, you're forced to replay the mission from its very beginning. Lost many hours already as it happens so rarely it's hard to get used to it.