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.