Strong disagree. The new mechanic forces teamwork and coordination to quckly react to enemy presence rather than the minigame that was respawn on command tent and fight. It needs tweaking and possibly AI need a rank and supply reduction to make it easier to defend bases to counter the strat of flying in with a chopper full of AI and dropping one at each base but the new system is 100% the right direction to be going. Most players ive talked to are in favour of the new system, its more realistic, it promotes teamwork, its more fun and it doesnt punish attackers for successfully killing enemies at the base. Its not a perfect system but to regress into the previous system would be an incredible mistake.

Hunter backpack is missing in which was Lemas (Rifle wrapped) and many other things which were in the backpack.

Today 22nd December between 22:05 until around 22:25 CET, there was extreme packet loss up to 90% at times, and intermittently red server fps on server 3000116. A few minutes after it ended, a lot of people lost connection at the exact same time (SEE VIDEO)

I think they should expand on the original capture mechanic. Previously you had to manually reconfigure a relay to capture a base. If you combine that with the majority presence at the base and then perhaps include more points to configure after a base is captured to make it usable otherwise you cannot use any structures in the base you could fix the issue. For example: living quarters (replace paperwork), vehicle maintenance point (restock spare parts), field hospital (sanitize equipment), ammunition supply point (resupply weaponry), fuel supply point (change nozzles). Each part of the base should be unusable until it is reconfigured. This way bigger bases would take a concerted effort to take and you couldn’t just have an AI capture bases while still not allowing spawning on bases under attack.

I agree that it should be back to the old timer mechanic. Adding back the ability to dig down radios to cut off spawns already does a good enough job of allowing for a siege on a base. One person capping shouldn't completely prevent us from spawning on a base.

I have this same problem on xbox series x/s. When i plug in the standard first party xbox headset the game crashes. If I don't use mic game works fine. I have reinstalled the game, checked connection, reset modem and reset xbox.

same

and when switch the map can take up tp 20

A lot of ppl have this. It lets to enter, but after ~10 min of tries, pretty annoying

Same here… i cant play :(

Yes, it should be.

I am having the same issue. Tried to login to the last server I was on, refreshed the servers multiple times, tried joining other servers, nothing is working

Server error

Same for me, hope the devs will fix that soon. I died on Livonia official server and I can't re-join to try to get my stuff back.

Make sure to also check out the attached reddit posts.

I agree.

That's not what I'm missing. It's the native implementation of gyro, haptic feedback and the adaptive triggers tailored to each individual weapon.

Reproduction steps:
1.Start new combat ops game mode

2. unlock a quick travel spot/save house
3. Exit to main menu
4. Continue combat ops

> Player starts back at original starting point with no quick travel spot/ save house unlocked.

I can confirm that issue.

i guess you could easily use the Steam Controller mapper

sit in the queue, once the queue is over and try to log in the game will say day z is not responding. (validated my files)

Same problem here . Playing in PS5.

I just watched a stream, and the streamer also had exactly the same error.
Seems a lot of people are experiencing this issue at the moment.

Ok, what I did, and it resolved itself, I had to give the server time to restart.
I still don't know what caused it, or how it resolved it.
I suspect it is a problem with the main server database, and the data for my character got corrupted.

I've had the same problem for a few days. I could log into my Nitrado server but not official - 0x00040034 error or0x00040036 errors even if i restart the game- once it says this account is already logging to the server, but then login and out of My nitrado server and then it comes up with 0x00040034/6 errors.

also getting in on windows 11 haven't found a workaround

This is happening continuously on xbox

Same here, in the FB DayZ page of my country there is a bunch of guys with the same problem

This should be sufficient for testing. On VR map placed a building to put the player inside of, then an opfor HMG gunner ~200m away, ensure player and AI have no line of sight to each other.

In T184255#2724426, @PR9INICHEK wrote:

1.3.0.25
The problem has returned

After a long time the game comes to life, but I get kicked out of the server and get this message

Can you open this ticket?

Me and teammate having same issue

In T187515#2724464, @Trueflames wrote:

I’d say they assign bug testing on a set day depending on what the actual bug is as well as it’s severity or how many requests a person has made, if you wanna see results with some of your requests I’d say chill out on it for now your pretty much posting a new task everyday

I’d say they assign bug testing on a set day depending on what the actual bug is as well as it’s severity or how many requests a person has made, if you wanna see results with some of your requests I’d say chill out on it for now your pretty much posting a new task everyday

I approve this message. Aiming with a controller feels awful in Arma reforger. People who comes from other FPS with accurate aiming paramaters have a hard time with arma reforger. So sad that arma reforger dont have better parameters for thumbstick. Hope bohemian will have a fix for this in the future

Same here, if it gives you the error, just try again, it will eventually let you in

It is a known problem with old CPUs, such as Core2 Duo. The issue has been fixed in performance branches. Unfortunately the fix has not made it to the stable branch yet.
So for now, switch to the performance branch.

same thing happened to me. i have tried logging in from the launcher and still not solved

1.3.0.25
The problem has returned

I am getting the same. I usually just keep trying to join the (official) server and eventually it works. It can take 1-10 times of getting the error before it works. Just started getting this error in the last week.