I got this too.
May be linked with the server FPS (Server CPU related so) ?

Best way to be sure is to try a very light mission and an heavy one on the same dedicated server.

Anyway client FPS shouldn't be limited by server FPS if that is the case.

I am not playing 404 Wasteland, not my type of game. I am playing coop only, and i seeing very poor FPS on these coop missions where all the single player showcase run very fine.

So i guess there is something on the multiplayer side affecting the local (player) FPS.

Added 4 screenshots so you better see what i mean.

Can't they make the guys inside eject and being alive rather than dead ?

You should also get the same from the main rotor, this one doesn't kill you also. I've tried by crashing into the sea and ejecting before the main rotor stop under the water.

Vote up for that, the same bug can be seen in ArmA 1 & 2. Looks like the new engine still had it on board !

Added capture 2->3 ; 4->5 ; 6->7

Sometimes you move a little and it appears/disappears, sometimes you just look around you and it appears/disappears

Maybe they can improve on the ToH flight model too before they add it in ArmA 3 ?

Play withSIX give the same issue "wrong password", and they still use the ArmA2 methods. So if anything change ? Or "-password" is part bugged.

If not nvg, maybe light stick for underwater (with the oxygen bubbles please ! :p )

Upload my 2 mdmp/rpt for tonight game.

Crash reason : PhysX3_x86.dll
Mods : no mods (neither server or me)
Island : Altis
Mission : Ahoy Invade & Annex (modified by NGBC french team)

Latest event while alive : My last action in the game on the second crash was when my chopper wheel touch the ground at the main air base of that mission. I was on the third person view while looking the wheel animation touching the ground.

Side note : I noticed on the second crash that arma3 process was using around 2Go of RAM. I got 12Go of RAM in my PC, so it can't get higher if needed, i guess there is a default limit in the process itself. Don't know if that can helps understand the problem with PhysX3 dll

I am now downloading the Development branch, i'll report any dumps i got while trying this one as soon as i... crashed

Crytek's Warface got a scripted thing like this. Probably harder to get it working in open world game like ArmA but that could be a useful feature in some situations.

I am not playing 404 Wasteland, not my type of game. I am playing coop only, and i seeing very poor FPS on these coop missions where all the single player showcase run very fine.

So i guess there is something on the multiplayer side affecting the local (player) FPS.

I got this too.
May be linked with the server FPS (Server CPU related so) ?

Best way to be sure is to try a very light mission and an heavy one on the same dedicated server.

Anyway client FPS shouldn't be limited by server FPS if that is the case.

I strongly recommand deactivate all "advanced game option" (exthread & co in the official launcher).

Manage to get rid of all errors/crash by not using them. Maybe a clue for some of you. They do not affect the playing (framerate or texture loading isn't better or worse with or without them), but the stability is top notch now.

Probably old useless stuff for ArmA 3 ?

[QUOTE]3. Desktop recovery:

The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, [B]some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications[/B]. [B]Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly[/B]. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.[/QUOTE]

Can you, please, update the game so we have the display back & running while a TDR happen ? That won't solve the problem, but at least we could resume our playing while not having to exit the game.
Can you search for information about that ? Ask microsoft what you have to do ?

I've experienced this while rolling back to an older driver, it was in Planet Side 2 and the game correctly worked after few seconds of black screen.

Got 2 crash in the game tonight, same driver hang up & recovered. So i am still forced to rollback to a very old driver which isn't very convenient as i play arma 3 multiple time in a week along others newest games.
I've upload arma 3 RPT & Windows RPT. Have fun reading them if you read us !

https://mega.nz/#!WYERRbYQ!stvAaUIX8S-BSszxtGa78aTA_YgpeMj6og-8vGKeukI

Of course i'll also post this information on the nVidia forums, hoping someone there will also want to investigate why the driver is so unstable with your game only or mostly.

I got the same bug, not only today. I think i got it since lots of months.
It happens to me in single player and multiplayer, most day i play arma for few hours i will have it at least one if not more.

Already tried to reinstall the whole PC (format), multiple nvidia drivers, 2 graphics cards (GTX 680/GTX 980), added the option so aero turn down itself when running arma3.exe, low/high/ultra settings, uninstall geforce experience, reset the nvidia 3D parameters to default presets.
Even arma RPT doesn't register the error, alt-tab doesn't work anymore (maybe because of aero disabled for A3) so i can't see the message, but no reason he has change as the behavior is the same.

ArmA 3 is the only game for now that hang up like this, guess i'll have to wait until i get a complete new PC if the developer don't know what is happening ?

Microsoft wrote this on their website :

"DXGI_ERROR_DEVICE_REMOVED
0x887A0005
The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. The application should destroy and recreate the device. For help debugging the problem, call ID3D10Device::GetDeviceRemovedReason."

But i guess only BIS can "call ID3D10Device" or whatever function is needed to understand what is the problem. At least, it's not something i can do on my own.

I also have it with a GTX 980, the only successful thing i have done is a driver rollback to 23th September 2014 GeForce Driver. Now the game is running fine, so it's also a problem in the nVidia driver. Already sent them tons of DMP (placed in C:\Windows\LiveKernelReports\WATCHDOG after each crash), but maybe Bohemia would want to look at some of them ?

[QUOTE=Last STIREP #00110]There exists a bad crash of various display drivers. It produces very little information besides a DXGI_ERROR_DEVICE_REMOVED message. We also know it happens in some other games, but don't deny that this update has potentially increased the frequency for Arma 3. While we work on a fix, we have spotted some users who claim success by downgrading their drivers.[/QUOTE]

So i can confirm rolling back is in some way a success, but some others games (newer) run bad which isn't great, and change driver everyday to play one game is not a solution ! :p
Anyway, while rolling back i got the same issue in another game (planet side 2 i think), but things went different. After the driver was reloaded, the game itself reset the display so i can see again without restarting the game (tooks only few sec by itself).
Maybe on that point Bohemia can do something ? Because the worst thing is not the error/display lost, it's that the game can't recover/reset the display after the black screen. You have to kill arma3 process or access A3 menu (escape) then alt+f4 to close it. And restart the game is a mission killer :(