Make sure you use ASL positions with intersect commands.
In your repro getpos won't work.

I am sure the developers will respond after they have returned from holidays (2 Jan). So likely later this week.

Oh. Any update on how to fix this?

@DJPorterNZ, try all of the possible solutions listed for 0xC0000005 - ACCESS_VIOLATION on the Arma 3 Unusual process exit article on the Bohemia Interactive Community Wiki.

In T122385#1556884, @aviatorboy1996 wrote:

I forgot to say that my CPU is the AMD fx 6300 and my GPU is the EVGA GTX 960 4GB FTW. Not sure if it matters.

@Carried, I cannot see any arma3.rpt files in that report file that you have attached. If you go to the below directory are there any arma3.rpt, arma3.bidmp, or arma3.mdmp files? If yes then please archive (zip) and attach them.

And I do have "C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.dll"
Should I delete it?

@saracenrush, a couple of questions:

I can confirm as well.
Same problem with RHS M252 (USAF) and 2b14 mortars (AFRF)

I forgot to say that my CPU is the AMD fx 6300 and my GPU is the EVGA GTX 960 4GB FTW. Not sure if it matters.

I have replaced the files correctly and have failed to run Arma III, also tried deleting the other system file, and then failed to run it again.

when it will be fixed?(

Just wanted to say I see the exact same thing too, as well as several others:

I can confirm this issue. As a result, the artillery fire module does not work properly for mortars in Ares Mod - Achilles Expansion (see Github).
Note that the current category "Firing from Vehicles" is not appropriate and should be changed.
In addition, the title is also misleading as the command just does not work properly for multiple rounds.

This is such an annoying issue, especially on I&A servers that make a lot of use of the group management

Sorry guys yes Arma is still not working. I got mixed up with my ticket on DayZ. This is still pending fix

In T122375#1556435, @SirBoston wrote:

Error Code: 0x80070002

In the correct installation of .NET Framework, there have to be a System.DLL on the exact path I've posted before. Otherwise the game launcher (and many other applications build on .NET Framework 4) can't work.

@CliPeuM, would you be able to try:

I'm assuming this problem is unfixable and have to wait untill 64 bit releases to the main branch.. Right?

I'm having the same problem in Windows 7-64 bit. Once I enable 64 bit Arma 3, TrackIR disappears from controls. Disabling 64 bit Arma 3 causes the controls for TrackIR to reappear.

@Tyreseb3, could you try the possible solutions listed here?

See also: T122586, T122588, and T122589.

@56curious, try the following:

@CalvinC, could you use the Arma 3 Launcher to prepare a troubleshooting report and then upload the report to the feedback tracker for the developers to review?

First of all: I wish you all a happy new year 2017! :)

I am rather surprised that this has not been addressed. It's clearly a bug. If you run the sample mission it would be obvious. It worked fine in A2, broken by A3. There are a number of other speech related bugs too, such as "say" command not working with lip files, which I believe otherse have already reported.

Also, I just attempted to run my Arma 3 in compatibility mode and an error came up. Here are the details:
Package ID: PCWDiagnostic
Path: C:\WINDOWS\Diagnostics\Index\PCWDiagnostic.xml
Error Code: 0x80070002
Source: Engine
User: DESKTOP-FB87KV4
Context: Restricted

Browsing through the files, my files are different from "System" and on. I have "System.Management.Automation". If that's the correct file, then I have the "v4.0_3.0.0.031bf3856ad364e35" file, then all I have in that file is an application extension called: "System.Management.Automation.dll". C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.031bf3856ad364e35
Maybe my version is different, as I have "v4.0_3.0.0.0...", and my system needs update?
Here's the "System.Management.Automation" file if you need it:

I remember posting an issue similar to this a long time ago too bad it got removed. I am glad someone else is still trying to fight this

Can anyone confirm? I had some issues launching 64 where it was launching 32 instead but i think i confirmed 64 was running and tackir enabled.

Actually not sure if its just me, but it's been working!

Would be nice to play with x64, but without trackir...nope.

Hello,
according to the report its an entirely different file "System.Management.Automation.dll", not "System.dll".
Are you sure that you've send a report for the correct file?

finally, I found the solution. The problem was the windows 7 x32 .now with windows 7 x64 Arma 3 works . thank you so much @Jawsh

@Mr.Epic, attach the troubleshooting report to the feedback tracker. If the report file will not upload directly to the feedback tracker then try uploading it to a free file sharing service such as Dropbox, Microsoft OneDrive, Google Drive, Mega.nz, and so forth, and then link to the report file.

It would appear this may have morphed into an internal application failure that does not "throw" any exception. I run two 24/7 Arma servers (Altis and Tanoa) that both intermittently fail as of the latest 1.66 patch.

email me

Thanks for getting to me so quickly. I have done those steps and now it is redownloading missing files from Arma. Thanks so much from the feedback. @Jawsh

@stax94, I am not able to download the report file. Could you please try attaching (drag and drop) the file to the feedback tracker or upload the file to a more reputable file sharing service? Some examples include: Dropbox, Microsoft OneDrive, Google Drive, and Mega.nz.

@Sebbo, a few questions for you.

This problem is still happening... it is weird you spend so much to update the game but don't fix something that is a big glaring problem that affects every moment in the game. I emailed Roderick from SIMUL and he said the problem was fixed on their version, but it will require BIS to update it on the game's version. This was in mid 2015, and I reported the problem then, but in almost 2 years since then, it has never been fixed.

im good now, thnx alot.

Okay here is the link: https://www.virustotal.com/en/file/d07b38d66c73ecda293c93643795a1f5d8b93d1e8685b243955cb0c31acddfb1/analysis/

Has anyone found anything yet?

It looks like in 1.66 this bug is solved. Tested it today with a friend again and I was able to lock onto the Laser designator and the missile tracked the laser too.

Hello SirBoston,
I'm sorry for the delay, I didn't forgot about you, but rather run out of options that can be easily done.

Just noticed that setting v-sync ingame disables Crimson framerate target control, if this might be related.

Duplicate of T122511. There was no need to create a new issue, @Hazard27.