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

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

Hello again :)

So a plan to deal with this is in the progress, there's something I need you to do so we can progress further.

If you won't mind, please, go through these steps

• Switch to latest Arma 3 "profiling branch" - Steam Branches
• Go into "Arma 3" directory in Steam and rename "arma3profiling.exe" to "arma3.exe" (Launcher and BattlEye are expecting that one).
• Launch game and start playing.
• Press together {L SHIFT} + {NUM -} (NUM Minus) and release them - Help
• Then just type "frame" (as with any other cheat mentioned in the Help)
• Should a dialogue stating it was successful appear, select "COPY ALL" (third button at the bottom row).
• Data should be copied to clip board so paste them (CTRL+V) anywhere you want (e.g. create a new txt file on desktop and paste the info there)

Once you have that file, please upload it here (or, if you encounter any trouble with that, to some free file sharing service and post the link here).

Thank you very much :)

Hi Buddy,
I did all the stuff as instructed above.
I did it on my local KOTH Tanoa server with my character standing in the spawn area.
Here is the rich text file.

Thanks for looking into it for me. :)

Also just encountered this crash when I reverted to the regular game (opted out of beta and replaced my arma3.exe with original)
I have had similar crashes pre-patch but maybe it will help you...

Exit code: 0xC0000005 - STATUS_ACCESS_VIOLATION

I couldn't upload the entire report so if you need it please let know.

Hello,

sorry to bother you again, it seems that the info about the "frame" cheat was not complete and I need you to try it out again one more time, but this time please play the game up until the FPS drop and freezing.

So sorry about that :(

Hey razazel,
I did it twice in one session for you. I hope it worked..

One more for good measure!

Thank you, much appreciated :)

Hello,

thank you for the feedback you have provided in this matter.

As progress in this case is moving forward, we are trying to pinpoint the cause, which unfortunately means yet another intel gathering.

A new profiling was published, rev. 137737, that will help us get more precise info about the issue.

Almost all of the performed steps are still the same, almost every of them only two things change:

• needs to be the latest profiling branch rev. 137737
• this time include also the rpt file from the session

Once you have those, ZIP them and attach them here again. One frame will do, more of them are very welcome (please make sure to have corresponding rpt as well).

Thank you