I confirm this issue.
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
Sep 4 2019
Did you have any issues before the update?
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Make a backup of and delete your .\Documents\DayZ\ folder.
Are your graphics driver up to date?
Sep 2 2019
This should be fixed in the latest Experimental version 1.05.152376
"Fixed: Audio of distant gunshots could be delayed or merged"
Unable to reproduce on 1.05.152376
Sep 1 2019
Do you also get this issue on DayZ Experimental?
Aug 23 2019
This happened to me months ago, but when I closed the door again I could walk inside, while the door was closed.
Aug 16 2019
Do you have a router?
Does your internet connection also get affected outside of DayZ when this happens?
Jul 31 2019
Did your friend log into your DayZ/Steam account on your PC or his/her own PC?
Jul 25 2019
This issue has the same crash error values T142587
Did you play another match before the crash, without restarting DayZ?
Jul 24 2019
This issue is identical to T142563
Jul 23 2019
It happened again, Steps To Reproduce followed.
This issue is identical to T142563
Upload your crash logs
I have received the same type of crash.
Version 1.04.152166 alphaSGmod
0xC0000005 - STATUS_ACCESS_VIOLATION at 9DD1E2F8 Unknown module
While I was spectating another player after I had died, I pressed Esc and clicked Exit, then DayZ crashed.
Jul 22 2019
Reducing the Ambient Occlusion setting only gives me +2 FPS.
Do you still have this issue and does Experimental also crash?
Set Stereo Mix as default input device in Windows to see if DayZ or Windows is the problem.
Things to try:
UNABLE_TO_INIT_DXIG means your graphics card could be the issue, try and update/reinstall your drivers.
Run as administrator ...\steamapps\common\Arma 3\BattlEye\Uninstall_BattlEye.bat then
Run as administrator ...\steamapps\common\Arma 3\BattlEye\Install_BattlEye.bat
Jul 1 2019
Are you still having this issue in update 1.04?
If so, try removing the -malloc=system parameter.
Did you recover FPS when you closed the inventory screen?
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Make a backup of and delete your .\Documents\DayZ\ folder.
Does it work? If not, upload crash logs.
When you crash, the game will most of the time generate crash dumps and logs that can be analyzed to find out why it crashed.
.RPT logs + dump files can be found in %localappdata%\Arma 3\. Take note of the date your game crashes and compare it with the date stamp of the dump files.
By placing them in a compressed archive and dragging and dropping it here, you can upload them for the developers.
I can reproduce this issue. It appears like light-blocking objects that aren't rendered at longer ranges won't block the light, making lights a lot more visible than they actually are.
Jun 30 2019
I can reproduce this issue on Stable, haven't tried on Exp.
Other people appear to be experiencing it as well T141567
What singing sound are you talking about?
How much RAM do you have?
Can you upload a dxdiag report of your PC?
This appears to be the same issue as you are having T141646
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Make a backup of and delete your .\Documents\DayZ\ folder.
Does it work?
I don't experience this. Are you playing DayZ from a HDD or SSD?
Does it help if you reduce your graphics settings?
Have you tried disabling HWAA?
Jun 2 2019
This issue should be fixed in Experimental Update version 1.03.151589 or higher, if you are affected by this issue switch to Experimental-branch.
Fixed: Turning Night Vision Goggles on cancelled personal lights of other players
May 31 2019
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Does Windows log an event in the Windows Event Viewer?
Ctrl+R "eventvwr" OK, check Windows Logs > Application and find the time of crash.
Can you upload a dxdiag report of your PC?
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Is the issue always on the same server? Have you tried another?
Make a backup of and delete your .\Documents\DayZ\ folder. Does it work?
Does it help if you disable your mods?
Which version of DayZ were you playing? Stable or Experimental?
If you don't restart, just rejoin the same server, does it help?
What if you join another server?
Which helicopters do you enter and in Singleplayer or Multiplayer?
When you crash, the game will most of the time generate crash dumps and logs that can be analyzed to find out why it crashed.
.RPT logs + dump files can be found in %localappdata%\Arma 3\. Take note of the date your game crashes and compare it with the date stamp of the dump files.
By placing them in a compressed archive and dragging and dropping it here, you can upload them for the developers.
May 18 2019
I'm also getting this issue when I emptied my found Mag_FNX45_15Rnd with 5 rounds. The problem is, unlike for you, my rounds didn't end up in any medical kits or other containers nor on the ground... I noted that at the same time, other items on the ground in the vicinity didn't show up on the Inventory screen, but further away other items did.
Experimental Version 1.03.151529
Other people are getting this as well with other weapons T139299
Other people are getting this issue as well T139299
Have you always had this issue or did it begin recently?
How is your disk access when this occurs?
It sounds like your system handles DayZ well but when your 8 GB of RAM gets used up, it starts to use the paging file instead.
Try and terminate background processes or get more RAM.
I just had this happen for the first time. I started up DayZ and logged on a server like usual. I was going to aim with my LAR and use the scope when it suddenly fires.
The firing mode was set to Full Auto. I Right Clicked again and immediately the LAR started firing again, without left-clicking.
Then I switched the firing mode to Semi Auto and aimed again, and it worked fine again without firing itself even once.
Experimental Version 1.03.151529
Maybe it has something to do with this line appearing 28 times?
SCRIPT: Random Jam - 0.556251
But I don't know how my rifle could jam if I didn't even fire it once, I only aimed with right-click...
May 16 2019
Might not be the same issue, but every 15 minutes I get a short duration black screen stutter.
May 15 2019
Make a backup of and delete the .XML files in ..\Documents\DayZ\ does it work?
If it still doesn't work, have you tried disabling your mod @JG27-VF ModsPack?
Does this also happen on 1.03 Experimental?
When you crash, the game will most of the time generate crash dumps and logs that can be analyzed to find out why it crashed.
.RPT logs + dump files can be found in %localappdata%\Arma 3\. Take note of the date your game crashes and compare it with the date stamp of the dump files.
By placing them in a compressed archive and dragging and dropping it here, you can upload them.
Do you have the .DMP file from your Windows folder?
Does this also happen on 1.03 Experimental?
May 5 2019
The issue is still the same in v1.92
Apr 26 2019
I was able to call in the helicopter and destroy it after it had landed, then returning to complete the mission. No crash on RC 1.92.
Can you confirm if you are able to reproduce this crash on the new Release Candidate v1.92, or is it fixed?
https://dev.arma3.com/rc-branch
Are you able to reproduce this issue on the next Release Candidate v1.92?
https://dev.arma3.com/rc-branch
When you crash, the game will most of the time generate crash dumps and logs that can be analyzed to find out why it crashed.
.RPT logs + dump files can be found in %localappdata%\Arma 3\. Take note of the date your game crashes and compare it with the date stamp of the dump files.
By placing them in a compressed archive and dragging and dropping it here, you can upload them.
Apr 21 2019
It might not work but try uninstalling BattlEye and reinstall it again on your system.
Sounds like something is wrong with your mouse.
Apr 20 2019
Which version of Windows 10 are you using?
Ctrl+R "eventvwr", OK then write down the version and build numbers.
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
Then uninstall BattlEye and reinstall it again on your system.
"a flash of black screen" usually mean something is wrong with the graphics driver. You can try and update your graphics driver.
Also, Windows almost always logs an error when this occurs, look up the details in the Windows Event Viewer?
Ctrl+R "eventvwr" OK, check Windows Logs > Application / System
Apr 13 2019
Can you describe at which point in the campaign did you crash?
Apr 7 2019
Many players want this feature, however this isn't an issue for those who don't, as characters from Third-Person enabled servers can NOT play on First-Person only servers.
Apr 6 2019
When did this issue start? I don't get this issue so it has to be your Steam installation. Have you tried switching between Stable and Beta on Steam?
Steam>Settings>Account>Beta participation
Apr 3 2019
Upload .RPT logs and dump files from %localappdata%\DayZ\ by placing them in a compressed archive and dragging and dropping it here to upload.
Try and validate your game files through Steam>DayZ>Properties>Local Files>Verify Integrity of Game Files.
What kind of error message do you receive and upload .RPT logs + dump files from %localappdata%\DayZ\ by placing them in a compressed archive and dragging and dropping it here to upload.
Mar 31 2019
Experimental Update 1.02.150958
Fixed: When opening doors for the first time, the whole building model can move slightly
Mar 25 2019
How does this appear to other players? The same as for you?
Mar 6 2019
The developers know about it and will hopefully fix this in the next update T137102
Could you be having the same issue as this person? T137280
Feb 26 2019
Make sure to run DayZ with the -dologs parameter and upload the .RPT log file from %LOCALAPPDATA%\DayZ\ by dragging and dropping the file here when this error occurs. That way DayZ maybe able to tell why the options won't load.
Feb 24 2019
Did you experience this on multiple different servers?
What server did this occur on?
I also experience something similar to this.
I get a feeling the zombie is too far away even though you take a step forward when you swing your axe.
Feb 21 2019
What kind of PC are you running DayZ on? How much RAM? 32-bit?
Which version of DayZ are you playing?
When did this issue start?
Do you have any idea what your system is doing when these issues occur through the Windows Resource Monitor?
Feb 20 2019
Was this on Experimental 1.01.150625?
Feb 19 2019
On which server did you experience this?
The server admin should disable the kicks. If there's no contact information I suggest switch to another server.
Feb 16 2019
It looks to me you shot too far to the left to hit him. I don't think the 3rd person perspective crosshairs in DayZ is dynamic, like in Arma.
This issue is known T136912
Do you still experience this on the new update v1.01/150505?
Feb 15 2019
This issue appears to be an issue with my own hardware configuration as moving away my Windows Pagefile from my SSD to my HDD fixed these freezes. Apparently my SSD hung for some reason.
Feb 7 2019
- I killed a guy with 2 shotgun buckets.
Feb 4 2019
Feb 2 2019
It looks to me like you were teleported below the ground, I doubt that this is due to a hole in the terrain.
Are you experiencing the same issue as this?: T136243
Did you do something special to trigger this?
Looks like client/server-desync to me, when you tried to swap your weapon onto the body something must've happened.
Pretty much everyone is experiencing this. How much RAM do you have, and are you playing with DayZ being loaded from a Hard-Disk drive or a Solid-State drive or faster?
Hopefully AI is improved in 2019
Does this happen on one or all servers?
Can you search servers through the DayZ Launcher? Make sure your text filters are empty.
Jan 27 2019
Have you tried updating or reinstalling your graphics drivers? Make sure to clean all settings, configurations and old files with the DDU tool. https://www.wagnardsoft.com/
Guide: https://docs.google.com/document/d/1xRRx_3r8GgCpBAMuhT9n5kK6Zse_DYKWvjsW0rLcYQ0/edit
Jan 22 2019
Sounds like the hive saved your gear when you were looting the guys, so your gear never got saved.