Hello Rixerod.
Are you talking about our launcher or some third party one? Have you tried to reinstall the game? Are you connected by wire or wireless? And can you do a traceroute towards one of the servers?
Regards,
Geez

Change. It. Back.

Hello cygnus37.
Infected hearing has been increased for this update.
Regards,
Geez

Hello 5sety4.
SKS still jams as it always did. BK-18 has never jammed since it is a single shot break action weapon, so it does not make sense for the weapon to jam.
Break action and bolt action rifles in general never jam as it is quite unrealistic for them to jam - except for cartridge failure - but we do not have this feature in the game.
Regards,
Geez

Hello CHIP_
Please click show details and prepare report and upload the generated archive to this ticket.
Regards,
Geez

In T181546#2616819, @Tiger1010101 wrote:

Do you have any updates?
Thank you.

Hello Jonathan.Pantano.
Please try the following:

Hello estein.
The solution is to periodically clear the logs as described in the other ticket. However I will forward this to the devs as suggestion if there is something that could be done.
Regards,
Geez

Thank you, we will investigate with BattlEye.
Regards,
Geez

Hello again.
Just to clarify.
The infected hearing has been increased for this update. This has been intentional decision by the devs.
Regards,
Geez

In T181655#2615957, @Geez wrote:

Hello everyone.
We have tested this on our end but we were unable to find any issues.
Regards,
Geez

Reinstalling battleye, windows, game.... none of it solved the issue.

Also had this happen to me on my own home server a few times when i threw grenades and flashbangs but they never produce any error messages or stacktraces other then 'access violation'.
Today I had a crash when accidentally walked into a fire barrel and was just about to take damage.
This is what that crash produced:

I would like to add to this. As a longtime official server enjoyer, my favorite past time is to build bases. Particularly deep in the forest. The one thing I feel would add to the challenge for base raiders, would be if there is a mechanism in place that removes the ability to tear down a watchtower wall or fence. The two solutions I came up with was one:

Attempting to isolate testing further, I'm able to reproduce this crash almost every time during the shutdown sequence:

Assigned ToAssigned To ADMINS

In T181558#2615663, @kuzyn wrote:

Basically the answer is here https://forums.dayz.com/topic/259783-dayz-update-125/?do=findComment&comment=2494547

In T181743#2616779, @LydHosting wrote:

Hello Steniboy. This problem has already been reported in another ticket : https://feedback.bistudio.com/T181638.
Follow this ticket if you wish to be notified of its correction.

I want to add this to the feedback.

Hello, I have been monitoring the packet loss and on these days the packet loss was again red (according to the icon):

An example of a crash when the hive is initialised :

------------------------------------
WIN-UTOF1UC2OFH, 01.06 2024 17:23:13
Unhandled exception

I can confirm, gas pumps in Toplin and Sitnik prior to 1.25 worked on my xbox console server. My members reported and I confirmed this morning that u can no longer dispense gas nor can u blow up the tanks

Do you have any updates?
Thank you.

can be closed, small animals are now using ragdoll to allow go thru.

Hello Steniboy. This problem has already been reported in another ticket : https://feedback.bistudio.com/T181638.
Follow this ticket if you wish to be notified of its correction.

Like @voudou reinstalling BattlEye didn't solve the problem for one of the users concerned. What can we provide developers to help them understand this issue?

In T181655#2616337, @sanguine00 wrote:

Intentional or not, I think it's strange that the developers aren't noticing a difference, unless I'm misunderstanding Geez' reply.

As others have stated, the AI itself isn't really in a state to be ramping up the sensitivity to this point. It just results in frustration and being punished despite doing the right thing. I'm assuming there was a reason the developers intended to "focus" on the AI last year, despite walking that back later on. They feel cheap.

I have my doubts this was intentional, though. It seems like they are ignoring the existence of visual obstacles.

I should also point out that we've had a few reports of this from players on our customers servers. I've passed on the method recommended by @Geez. I'm waiting to feedback from these players.

Same issue since patch 1.25...

It seems memory gets overwritten while loot/eventspawner is doing something.

In T181655#2615957, @Geez wrote:

Hello everyone.
We have tested this on our end but we were unable to find any issues.
Regards,
Geez

our users are randomly reporting this as well

I wanted to inquire if there is an estimated timeline for a resolution to this issue.
Understanding that development and bug fixes can be complex,
any information on when we might expect a fix or update would be greatly appreciated.

In T181594#2616237, @Geez wrote:

Hello Sm0ky.
Maybe something else uses the port already? Could you try using a different one (like 1xxxx) and see if anything changes?

Intentional or not, I think it's strange that the developers aren't noticing a difference, unless I'm misunderstanding Geez' reply.

FYI, I'm able to usually reproduce the crash by sending a manual rcon shutdown. It is not 100% consistent though.

In T181655#2616238, @JerryK wrote:

And they seemingly react to door opening sounds. Okay... but can we please stop slamming the doors? Can I open/close them slowly like a rational person would?

I like that they are more aware now, but some scenarios don't make sense.

Hello Sm0ky.
Maybe something else uses the port already? Could you try using a different one (like 1xxxx) and see if anything changes?

it's fairly evident the Infected are much more aware of players and noise - it's nice to see them reacting to doors being opened (which was in patch notes some versions back, but didn't seem to really work back then).
I was able to sneak attack a fair number in broad daylight by crouch walking on grass with hiking boots, and even some other terrain - but they are definitely MUCH more aware than 1.24.
Our players are really only bothered by this because infected behavior is still janky as hell. - being hit from yards away, being hit when the infected isn't facing you, stuttering around (our server performance is excellent but yes this is desync), new warping through doors
I think if BI could get much better consistent behavior from Infected most of the complaints would subside.
As some of our players put it - I'm doing everything right and still being hit - it's frustrating.

They informed that there is nothing wrong with My connection. Problems started 30.5

I can also confirm that zombie hearing is not affected by rain. They are aggroing from much further away. If this is an intended change to zombie behavior, can you confirm?

Thank you.
When did this issue start to occur?
We think, this might be network related issue, perhaps consulting this with ISP might help, latency seems a bit off along with hop timeouts.

The infected being able to hear doors open and hearing you through walls is intended?

Hello KobaconGaming.
Can you please try to reinstall BattlEye?
Batch scripts for installing/uninstalling BattlEye are located in the game installation folder BattlEye

Seems to be happening same time at night{F4018207}

Unrelated apparently ...
It didn't fix it

Tracing route to 195.82.158.110 over a maximum of 30 hops