Yes, the 1.10 Changelogs indicate this feature was implemented, but it either does not work, or it is not clear on how to use it. Priority.txt is locked during runtime so it's not possible to edit it on the fly.

DayOne is seeing a 60-70% decrease in server FPS as of the 1.10 patch. During normal operation it is playable, but there is no headroom for the frequent performance dips which result in the typical issues (doors and inventory lagging, players stuttering, awkward zombie combat, desync).

I don't think it will matter, moeb1us. We've already increased spawns around Sitnik, Grabin, etc. with only marginal success. The ultimate goal is to be able to configure the spawn system so that it simply selects spawns using "pure RNG".

It seems like some older persistence backup must have gotten in the way of testing, because after another wipe I can't reproduce this issue. Sorry for the erroneous report.

I did some more testing and it seems that when shooting a dummy with buckshot from ~10m or so away, it only takes 2 shots to kill, but if you walk up to the dummy and shoot them at point-blank, it takes 3 shots. It seems like the spread of the pellets gives it a better chance to hit multiple hitboxes on the player, which amplifies the damage.

It looks like this has been resolved as of the June 18th Experimental release (1.08.153212). I dropped my spawn jeans and a ruined steak knife and logged out to watch the logs:

Yeah these comments will always cause the file to fail validation. Might seem like a small thing, but it's definitely an annoyance if you regularly validate your mission files to avoid errors after edits.

From what I've seen, multiple people can cook on fireplaces placed on the ground outdoors, but not on ones placed in the indoor ovens/fireplaces.

Maybe he put some of the cooked meat in his shirt or pants?

In my experience this is hands desync. It's usually the same reason why bullets aren't doing damage, either. Relog "fixes" it.

Had players despawn within 30 minutes on our server, today. Our setting:

@JonDoug Were you putting the cooked meat in your shirt or pants? Warm meat will overheat you if you put it in your clothing. You have to put it in your backpack.

My buddy and I were able to get a 100% repro of this bug by killing someone as they were firing their weapon. In our case a AK74 on full auto. No other scenarios we tried could reproduce the bug.

This is still an issue in 1.05:

The reverse of this is also true. In Arma and DayZ legacy, you could raise your weapon and still use eye focus, which was helpful for scanning areas while in an offensive/defensive posture. Now you get thrown in to ADS when you attempt to do this with the weapon raised.

Maybe it's my display, or an issue with my eyes, but I still can't see anything at night (which is a good thing). The sky seems a bit brighter, which allows you to separate it from the horizon and navigate long distances a bit more accurately, but at ground level I can't see a darn thing without a light source.

Glad other people are noticing. It looks ridiculous.

Having the ability to "Include" other types files with a single directive in the main types.xml would be a quality of life enhancement for modders and server admins.

Just throwing in my two cents: we had a friend on 1.05 Exp. in Novy shooting zombies with a MKII (Amphibia), we could hear the shots from Guglovo. It sounded as if the shots were coming from inside our own heads.

I've found that these init.c settings not only start the server with a clear day, but prevent the weather from rolling in later on (if you're into that):

@markyc2005 If he's not sure which mods don't need to be running on the client, it's probably safest just to set them all to be client-side, rather than server-only.

@markyc2005 Does your friend use OmegaManager to deploy his server? If so he needs to pull an update for OmegaManager then verify his server files.

@Geez I tried with several different types of head wear on 1.04 Experimental, and can confirm the issue is fixed. Thank you!

@ChawDinky Many other servers had this issue at 1.03's release (Including DayZ Underground and Usonia). They found it to be related to opening base gates that had been built prior to 1.03.

Was seeing this repeatedly on ExecCS's stream last night as well. This only happened after waiting in a long queue, so we speculated that by the time the queue system tries to join the server, perhaps the auth ticket had timed out. Maybe the queue system needs to take steps to refresh or keep alive the auth ticket?

There is a bug that can result in the Vicinity screen scrolling down even though there's nothing to scroll down to.

Please disregard this report and see @Gews much more scientific report here:

I've seen behavior resembling this, as well. It is reproduced by dragging a magazine into your inventory when your gun has no mag installed and there is no room in the inventory for the magazine to go.

This also happens if you use stick+rag to make a fireplace (the rag disappears).

@avix are you talking about the low-frequency rumble that begins as you approach an area with buildings?

Thanks @Geez . I did some testing myself and found I could only recreate the issue with a window that is set to "Always on top". So if an "Always on top" window (like a messenger app or TeamSpeak) is bleeding into the primary display, it should trigger this behavior 100% of the time.

I've also experienced this issue but not just when clicking in on a window or the desktop while the game is launching. It can also happen in multi-monitor setups if you have a window from a non-primary display touching or spanning the border of your primary display at the time you launch the game.

Noticed this since the introduction of the new renderer. It seems like mouse sensitivity spikes up with the FPS in some ways, and is most evident when you are standing up against an interior wall.

Thanks Geez.

Throwing in my 2 cents as I'm a dedicated 2xW'er:

This happens to me when I approach our base. I slide around a bit and cannot turn (only strafe). It eventually subsides.

Found one in front of the church at Pustoshka:

Do you have a multi-monitor setup?

Same exact issue here multiple times while playing on the Experimental build that was pushed to Stable today. Like you said, dealing another blow to the infected's corpse is the workaround.

I know the devs are aware of the issue, but I wanted to add a clip I saw from a streamer today, as I think it's a perfect example of the issue. Maybe it'll help, maybe it won't.

I've seen the lag in close quarters combat happen to multiple streamers over the last couple days. It just chunks up like the old days when a game was loading textures off your 5400 rpm hard drive. (obviously not the same issue but that's what it looks like).

Noticed this on Experimental, as well. All tires and parts pristine. The vehicle controls fine on the pavement, but once you take it off-road, it's like you're on ice.

I had this same problem with the December 7 build as I was approaching NWAF. My buddy and I were running together and both our games slowed to 1 FPS, his for roughly 1-2 minutes and mine for about 4 minutes.

In T117992#1542154, @theclassifiedrebel wrote:

I doubt there will be a fix anytime soon for this since it has been since July and they still have not even said they are looking into it

I've had something similar happen with ammo stacks. I'm not positive it's the same bug. I picked up a "pristine" stack of 20 SKS rounds in Kamishovo of all places. The server crashed a few minutes later as I was headed to Staroye. When I logged back in, it was now 7 rounds of "damaged" SKS ammo.

The current workaround to get game capture to work in OBS is to disable antialiasing.

For me anyway, I'm able to get my face back by removing my gloves. Putting them back on does not immediately trigger the bug, but sometimes it returns later on.

Character wipes are part of the deal with Experimental. You should expect a character wipe with every new build, and if your character survives then you should consider yourself lucky.

Definitely still noticeable in Test #4, but improved.

If the problem is related to players hearing (certain) gunshots, that would explain why the servers crash more frequently after an hour or so, as it would coincide with more and more players picking up weapons and shooting them.

I was having this issue in Exp Test #1, as well (didn't get to jump on Test #2). Apparently an emerging common denominator is 144Hz monitors (I have one as well). Would be curious if other people contributing to this report also have 144Hz monitors.

Gonna jump in and comment that with the release of 0.60, I was getting a black screen in OBS Studio when using Game Capture (Windowed mode worked, though).

I've seen this happen, but only while inside some structures. Try panning around with a red dot while inside a military tent and you'll see the red dot disappear.

DayZ .60 requires a Directx 11-capable card. The GTX 285 only supports up to Directx 10. :(