- User Since
- Dec 5 2015, 7:20 PM (338 w, 17 h)
Mar 26 2022
Mar 6 2022
Hopefully this gets addressed but, in the meanwhile, I've created this script snippet to identify modded clothing items that may generate the error:
Feb 19 2022
Jan 29 2022
Nov 10 2021
Nov 8 2021
Nov 6 2021
Oct 26 2021
Oct 2 2021
Direct steam:// links for connecting to DayZ servers are extremely useful and time-saving for users, as the launcher's server browser can take several minutes to load the complete list of community servers. Please fix this so that there is a way for server admins to create reliable direct links for users to connect.
Sep 14 2021
@dedmen Hi, thanks for your response. I'm not sure that is true about absolute paths not being supported.
Sep 11 2021
Sep 9 2021
Sep 8 2021
Sep 3 2021
💖 1.14 💖 Thank you @Geez and the DayZ dev team! 💖
Aug 2 2021
Thanks @Jacob_Mango for the helpful tip!
Jul 17 2021
May 15 2021
Apr 1 2021
Potato skins are delicious when cooked!
Mar 20 2021
@mate26 You can't open that file because it has already been opened for writing by the DayZ process.
Feb 13 2021
Jan 29 2021
This is still happening on DayZ Experimental 1.11.153696, as can be seen in this Twitch clip: https://clips.twitch.tv/AntediluvianSpookyFloofDeIlluminati
Jan 24 2021
I agree that this ticket should be closed. I don't know when it was fixed but I have checked multiple instances of this building in 1.10, including the one at the Stary Yar/Krasnoe logging compound, and the doors are showing the correct "Open" and "Close" actions corresponding to their states.
Confirmed this is fixed in 1.10.153598 by connecting to a local vanilla server:
Jan 10 2021
Hi @Geez . It looks like this issue is not fixed in DayZ Server version 1.10.153598.
Jan 3 2021
Yes, adding the -limitFPS=200 command line argument appears to work around the issue.
Jan 2 2021
May be close this ticket because it's obsolete?
Hello @Geez! It seems like ScriptCallQueue completely stops working after a server has been running for over 4.5 hours. My mods depend on ScriptCallQueue so I have to restart my servers every 4 hours to work around the problem.
Dec 28 2020
Dec 16 2020
Dec 13 2020
Sep 7 2020
This bug is not limited to just the revolver and Blaze; I've also seen this happen with the BK-43 and the SKS. It might affect all weapons with internal magazines or multiple chambers.
Jun 14 2020
@ukulelekid713 Removing the "if null, will send to all players" comment sounds fair if there is no intention to support null for the player argument. However, I think a notnull modifier should also be added so that the function doesn't silently ignore incorrect usage.
Jun 13 2020
Apr 26 2020
Apr 11 2020
Sep 14 2019
Sep 8 2019
Apr 6 2019
I agree with @PR9INICHEK . This was likely fixed with the new engine as I haven't seen the issue or other texture glitches like it in a long while.
Jan 8 2017
Dec 9 2016
Zip file containing minidump files is here: https://drive.google.com/open?id=0BwmKlzmmkZAdXzEycDg1R2dydTg
Dec 8 2016
Jun 19 2016
May 11 2016
This issue appears to affect all pump station buildings, not just the one mentioned in the description. I've reproduced the issue at 2 other locations. I have also attached a screenshot of the building.
I am also experiencing this crash. After I exit DayZ, a dialog box pops up, titled "DayZ.exe - Application Error", with the text, "The instruction at 0x77dbd968 referenced memory at 0x00000014. The memory could not be written."
The crash is consistent for me. It has occured every time I have exited DayZ.
My system is running Windows 7 Professional Service Pack 1 (64-bit).