ImpulZ

On the weapons you mentioned, they are roughly taking 80-90 shots to ruin a pristine suppressor, which with an SG5-K can be only 3x 30rd mags, with the IJ-70 it's 8+ mags. The intend is to have suppressors ruin faster than the base weapons, and force players to choose when to use them. At the current stage, head-shooting up to 80+ infected seems like a fair use for one suppressor in our opinion. But this might change over time, we are reading the feedback and impressions here and on our other socials.

Could you specify which weapon you are referring to here?

DayZ Staff can not and do not have access to BattlEye global or VAC bans, and can not revoke them in any way possible. You MUST contact the BattlEye (in case of game ban) or STEAM support (in case of VAC bans) about any bans issued on you. Closing the topic.

DayZ Staff can not and do not have access to BattlEye global or VAC bans, and can not revoke them in any way possible. You MUST contact the BattlEye (in case of game ban) or STEAM support (in case of VAC bans) about any bans issued on you. Closing the topic.

So you are switching between two differently modded servers in one game session? Mods are initialized when starting the game, so you might need to restart the game to connect to the new server. The launcher is an easy way to do this and have your mods automatically adjusted, once you have both servers added as favorites.

DayZ Staff can not and do not have access to BattlEye global or VAC bans, and can not revoke them in any way possible. You MUST contact the BattlEye (in case of game ban) or STEAM support (in case of VAC bans) about any bans issued on you. Closing the topic.

You appear to be playing on PC, please refer to the PC Troubleshooting section with details on your server (community, official, modded or not etc) and the exact error message.

Hi, can you send us the exact text of the error message please? And to clarify, you have tried to enter multiple official and community servers, and always received the exact same error? What you can try is, verify your game files via Steam (right-click Dayz in your steam library -> properties -> local files -> verify integrity - check all boxes)

You install DLC in Steam by going to DayZ in your Steam Library, and either in the Properties->DLC or on the right-hand side you will find a box labelled DLC where you can manage your DLC (including checking boxes to install/uninstall). The "DayZ Experimental" app is our experimental branch where we test updates publicly before they hit the main game.

DayZ Staff can not and do not have access to BattlEye global or VAC bans, and can not revoke them in any way possible. You MUST contact the BattlEye (in case of game ban) or STEAM support (in case of VAC bans) about any bans issued on you. Closing the topic.

DayZ Staff can not and do not have access to BattlEye global or VAC bans, and can not revoke them in any way possible. You MUST contact the BattlEye (in case of game ban) or STEAM support (in case of VAC bans) about any bans issued on you. Closing the topic.

Hi, moving the topic to troubleshooting. Do you have this issue on official servers as well, and also with empty inventories? Feel free to upload a screenshot of your inventory, so that we can investigate this issue.

Cleaned up several comments focusing on provocation instead of actual discussion. Hint: If you spend all or the majority of your comment attacking another user instead of arguing your position, do not press Submit.

Removed some off-topic comments. Please stick with the topic of the individual discussion.

Can you give us more information on this please, when is it happening (e.g. after falling uncon or so)?

Hid several posts due to off-topic discussions. Please focus on the update at hand and feedback to it. Open separate topics for other discussions.

Game bans can only be appealed at the BattlEye support, our anticheat provider. VAC bans have to be appealed with the Steam Support. Closing this topic.

And just to highlight that we are aware of the topic, the description of the status given above is basically correct. Since the re-implementation of vehicles there have been these cases of instability caused by bad physics simulation. Physics and server-side vehicle simulation are quite complicated things, and while over the past 2 years there have been attempts to stabilize the situation, sadly it wasn't completely successful yet. As many players report, it's definitely not a thing of "you will fly into space every day", but it definitely happens in individual cases, and as the video nicely shows, it's something that looks impressive and anyone seeing it will definitely post it on YouTube, once it happens to them. As it understandably in most cases involves the dead of the driver and fellow passengers, it's only a laughing matter at first. Our engine team is aware of the issue and regularly allocates time into investigations on this to find improvements, as you can imagine this kind of a situation is nothing a programmer likes to see as the result of their work either. Due to the proven complexity of this topic and other work within the engine, we are sadly unable to give an ETA as to when this will be fixed. As many other things in the game, vehicle simulation is calculated server-side to prevent hackers from abusing them. Sadly it can result in these instabilities in cases of bad connection, that aren't always clearly reproducible. Another aspect are ground collisions, as we've observed cases where vehicles would show irratic behaviour after having wheels added. That said, we'll provide updates to this topic if anything changes about this status.

We have indeed confirmed some issues with the splitting action and yield, we're investigating. Will check these. This is intentional for the time being, we'll see how we can replace it in the future. 🙂 In the current version, you should die from one .308 shot to the torso (if you're not wearing armor).

As we wrote in the changelog: "Unconsciousness time is now modified by the caliber the player got hit with." So to clarify, it's not always 7 seconds, it can be longer depending on what knocked you out. This change is a follow-up to our changes in 1.12 that resulted in more players falling uncon during combat. I highly recommend to try it on Experimental yourselves. I said that in this discussion we consider it "derailing the topic". So you can feel free to open a dedicated thread here on our forums. But continued discussion of the state of vehicles in this thread will be considered spam, as it's in no way related to our changelog.

Let me not take you literally, because we probably did not use that exact phrasing, but we've acknowledged the issue several times. Some examples are here and here. This state is still ongoing, sadly. I also see that you continue to derail the Experimental discussions to hammer on this topic. While we understand player's frustrations about the vehicle problems, this does not put you above the guidelines in terms of spam, cross-posting, and bumping topics of your personal interest. So please keep your "reminders" at a decent level without distracting from actually relevant community feedback. Rest assured that your opinion is received and noted, but everything beyond that is just you yelling the time at the clock, figuratively speaking. This is intentional, sadly in previous builds we had to simplify it due to an error related to the saving of locked doors. That one should now be resolved, so we can randomize door states to make player-presence less predictable. It shouldn't be the case that you have to rely on meta-gaming logic like "there was a restart 5 minutes ago, so all doors should be closed". While I have to admit that "all doors open" will probably still alert you of player presence.

This is how the M16A2 works in real life. It's actually more punishing IRL, if e.g. you would fire only 2 shots in one burst, your next shot would only be one, before you could do the next 3 round burst.

This is still on our to-do list, sadly it did not make it for this update. It's sadly not as easy as just changing a number, as we also want players on PS4 to have a stable experience without too extreme frame-changes. You can still feed them rotten food. It was removed as we added additional functionality to the desinfectant items due to technical constraints. We clarified it a bit better in the changelog now, this is mainly about behavior of the game while you alt-tab out of it. You can either freeze the game completely, have visuals moving, or both sounds/visuals active while not focused in-game. Also clarified this part in the changelog now, 1 is for visuals only, 2 is for both visuals and sounds. If you want it to freeze, just remove the parameter. Because they are disinfected. It wouldn't be fair to players to have the chance with any fight from the start at the coast to get the wound infection immediatly, so we give them 2 "save" chances to bandage (the bandages don't spawn with full charge), afterwards they will have to find clean bandaging material/disinfectant. Which does not mean that every weapon spawns with a mag. Just that when you find a weapon with a mag, it has at least 1 bullet in it. Depends on the point of view. It seems more fitting to us that infected would search for a new target once one is incapacitated. It gives players the chance to escape from tense situations (you're mostly in a bad spot when infected hit you uncon, and they will probably still be wandering around somewhere close after you wake up) and we trust that it will make fights more interesting when infected switch targets from unconscious players to active combatants.

Okay, the truck is at least 100m+ away, I guess? Basically, the problem is caused by very large bases at the moment, and lot's of things loading in. So the more empty you have your immediate spawning location, the better. If you are on an official server, you can connect to a different server briefly to reset your spawn position to the coast, which would allow you to rejoin your server again. Otherwise you would have to try and clean up your spawn location a bit and see if that helps. As I mentioned above, it's a known problem on our side, and we expect to improve the situation with our next update.

Hi, there are some known issues with this specific error appearing. It could be tied to the M3S truck, in case you are logged out close to one. We expect this issue to be fixed with the next update.