Still happening with 1.26.159040

Still happening with experimental 1.26.159034

@Geez It looks like this bug has been fixed in DayZ 1.21

I, also, appreciate this config change as an improvement. When I noticed it about a week ago, I went ahead and updated my clothing configs to work with the new inheritance.

In T170796#2416700, @Nate_LapT wrote:

...causing everything to crash and requires the launcher to be restarted to function.

@Geez It looks like the launcher is version 1.6.155752. Does the launcher not get updated automatically when Steam updates DayZ?

A significant part of the problem is that the official launcher does all filtering client-side, which means the client has to download the entire list of 9000+ DayZ servers from the Steam Master Server before a filter can work comprehensively.

Hi, friends! I see that this bug has gathered quite a bit of attention lately, due to it affecting Deer Isle vault doors and the suit printer on Namalsk.

Nice find, @lava76! Thanks for digging in and finding the root cause of T163613.

This is still happening with DayZ 1.18. I just had it happen again on one of my servers.

Hopefully this gets addressed but, in the meanwhile, I've created this script snippet to identify modded clothing items that may generate the error:

In T150034#2253643, @RandomHost wrote:

In 1.14, every mod which is not a DLC displays the default widget text, a rather unimaginative W, instead of the actual description.

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.

@dedmen Hi, thanks for your response. I'm not sure that is true about absolute paths not being supported.

💖 1.14 💖 Thank you @Geez and the DayZ dev team! 💖

Thanks @Jacob_Mango for the helpful tip!

Potato skins are delicious when cooked!

@mate26 You can't open that file because it has already been opened for writing by the DayZ process.

This is still happening on DayZ Experimental 1.11.153696, as can be seen in this Twitch clip: https://clips.twitch.tv/AntediluvianSpookyFloofDeIlluminati

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:

Hi @Geez . It looks like this issue is not fixed in DayZ Server version 1.10.153598.

Yes, adding the -limitFPS=200 command line argument appears to work around the issue.

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.

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.

@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.

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.

Zip file containing minidump files is here: https://drive.google.com/open?id=0BwmKlzmmkZAdXzEycDg1R2dydTg

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).