Manhim

That.

If I go into a chopper while in base and open my map, I will hear the chopper go by and still be able to hear everything that's happening at base like if I was still there.

This is all from the current build, going to test the dev build soon. Faulting application name: arma3.exe, version: 0.54.103.957, time stamp: 0x516582ca Faulting module name: arma3.exe, version: 0.54.103.957, time stamp: 0x516582ca Exception code: 0xc000001d Fault offset: 0x0000cfb1 Faulting process id: 0xd14 Faulting application start time: 0x01ce39fb9a3e688f Faulting application path: E:\SteamGames\steamapps\common\Arma 3\arma3.exe Faulting module path: E:\SteamGames\steamapps\common\Arma 3\arma3.exe Report Id: d81beb85-a5ee-11e2-be7c-3085a98fef19 Faulting package full name: Faulting package-relative application ID: Followed by: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Arma 3 Alpha because of this error. Program: Arma 3 Alpha File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0 Notice how the "File" value is empty and the Error value is 0. I also have a few of these: Faulting application name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6 Faulting module name: PhysX3_x86.dll, version: 3.2.3.1, time stamp: 0x50f68ef3 Exception code: 0xc0000005 Fault offset: 0x000d6dd7 Faulting process id: 0x1790 Faulting application start time: 0x01ce38a55d223f04 Faulting application path: E:\SteamGames\steamapps\common\Arma 3\arma3.exe Faulting module path: E:\SteamGames\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 07cb86ef-a4a1-11e2-be7a-3085a98fef19 Faulting package full name: Faulting package-relative application ID: And these: The program arma3.exe version 0.52.103.507 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 1d88 Start Time: 01ce3878be9d4a2f Termination Time: 4294967295 Application Path: E:\SteamGames\steamapps\common\Arma 3\arma3.exe Report Id: 6df50a29-a472-11e2-be7a-3085a98fef19 Faulting package full name: Faulting package-relative application ID: Hardware: - CPU: AMD FX-8150 - 16GB of RAM DDR3 - Main drive is SSD, Arma 3 is installed on a RAID-0 array of 2 1TB hard drives through Steam. - OS: Windows 8 Pro x64