And another Crash on Exp. 1.3.0.84 from yesterday

I can confirm the same for Utopia Airdrop, i disabled all Drops and the server ran without a Single Crash for 4 days now. Yesterday i tried popping an airdropflare and as soon as the Helicopter started flying the server crashed

I am sharing a screen recording to show you how significant the problem is. This issue occurs not only at the moment I first spawn but also at various points in the game. For example, when I drive to a combat area and exit the vehicle, the weapon in my hand and its scope fail to render. This makes it impossible to play the game in situations requiring quick reactions. Since the scope does not render, I cannot see elements like the red dot, etc., associated with the scope. As a result, the game essentially comes to a halt for me for 10-20 seconds. Additionally, while driving, the roads sometimes fail to render, giving the impression that I am moving on a flat gray surface. There are many other similar issues that I cannot fully list here.

I’ve been wondering this too.

I have disable my Expansion Airdrops now and since there, the Server runs normal.

I don’t remember exactly what I had in my backpack, but I know I had a rangefinder and a hatchet, but I’ll take an ak-74 haha just kidding that would be nice though to compensate you know?

I encountered a strange crash. For example, my server has been running for a long time without players. When I join the server again, the server will crash. After restart, I join the server. Everything is normal

Really looking forward to this one the most

It takes way too long to build up inventory just to watch this game glitch it away from you. I'm a fairly new player and logged 500hrs since August 24, This update wasn't great, has a lot of issues when I walk I hear my footsteps when I stop, my items disappear in walls or etc. just nonsense.

Yeah I experience this too, this new footstep audio crap is very annoying.

Agree. The new footsteps sounds in general do not sound good and it really throws me off because it sounds like someone is near me but they arent. Really don't understand why they changed something that was fine.

^ That's some bot advertisement spam

I sometimes also have this issue, but since 1.26 already!

In T189290#2761413, @OGBDayz wrote:

What does a dayz server try to do roughly hourly? at basically an hour +2-5 minutes my server crashes. If it makes it past the first hour it will probably crash at 2 hrs + 2-5 minutes, if it makes it past that it's a crash at 3 hours etc. It still appears to be related to the server saving or checking save files on people as seems to be mentioned above. What am I missing? I have all events turned off and still crashing, so it's not them

What does a dayz server try to do roughly hourly? at basically an hour +2-5 minutes my server crashes. If it makes it past the first hour it will probably crash at 2 hrs + 2-5 minutes, if it makes it past that it's a crash at 3 hours etc. It still appears to be related to the server saving or checking save files on people as seems to be mentioned above. What am I missing? I have all events turned off and still crashing, so it's not them

Same here, happened when there was a desynch once, the other time was no desynch

I have this too, but it's with any weapon.

In T189290#2760859, @Corse wrote:

Ok doing some troubleshooting on my servers I have been able to replicate the weird behavior.

Currently, I have only a few mods (expansion ai, expansion, expansion core, expansion quests, vppadmin).

I fresh wiped everything. Players.db included. Started up deer isle. Ran around for 30 minutes, no issues. Restarted the server, no issues.
Ran around for another 10 minutes or so, restarted the server, came back in, immediately got the access error.

Before I did this, I backed up the playerdb in a known current working state. I stopped my server, moved the backed up players.db into players.db (renaming the now non-working one to broken.db).
I restarted the server doing absolutely nothing else, and was able to join immediately, obviously with everything where it had been backed up. I took note of what i've been trying to do to recreate this when it happens, the only difference is, just before a server restart, I have been looting just prior. In this case, I had just grabbed a bag, an ak101 and a mag and forced the server to restart as I wanted to make sure it was saving stuff correctly. Upon coming back in, access error, freeze, and on and off server crash.

To test and see if it was players.db, I moved the newly not-working players.db to "broken.db" and copied the original working one back to players.db, restarted the server, and got back in yet again. I made no other changes to anything other than players.db.

In my logs, there are no clear errors I can see in error logs or rpt, it just shows "no packets received from player."
Feb 28 20:30:03 localhost startdayz.sh[12764]: 20:30:03 [Disconnect]: Client (Myid) early disconnect
Feb 28 20:30:03 localhost startdayz.sh[12764]: 20:30:03 [Disconnect]: Start script disconnect (Myid)(dbCharacterId 1 dbPlayerId 1) logoutTime 15
Feb 28 20:30:04 localhost startdayz.sh[12764]: 20:30:04 [Disconnect]: No packets from (Myid)
Feb 28 20:30:04 localhost startdayz.sh[12764]: 20:30:04 Player CaptainFlatulence ((Myid)) kicked from server: 4 (Connection with host has been lost.)

To manage to recreate the behavior I just need to have recently had the server normally save, be looting something and force a restart and it seems those players suddenly have the issue.

Sometimes, this results in the server crashing. Other times, the client side just gets kicked with an access violation after freezing. Verified this behavior can be reproduced on linux and windows servers.

10 years later, the game is still unplayable lmao

Me and my friend decided to go "out" with a car and we were saying "we'll be back on the coast in 2 minutes with this lag, guess what ! I was driving the car when I got kicked out (because it seems, a lot of players get kicked when it's too laggy), the car went into a tree because I got kicked, got to respawn and my friend was badly injured. I can't believe it, 10 years of development, I can't believe those "devs" can't make a stable fucking game in 10 years and are still adding shit update after update when we're asking for good stuff like diverse weapons, base building equipement, new vehicules but no, there are cheaters, desynch with the server and they are adding new "sounds" to weapons. Amazing.

Still getting this error.

@Geez @dedmen it might make sense to merge https://feedback.bistudio.com/T182075 and https://feedback.bistudio.com/T93061 into this bug, or at least link them - they are definitely related.

I can also confirm the error. I only have CF and COT and if I plant anything and the server restarts during growth, the growth status does not change and the plant never matures. 😣

I've also tried OPENSSL_ia32cap=~0x200000200000000 to really make sure its not a mix of hardware / too old openssl - but the issue stays the same.

Mar 01 17:30:59 game002 hashima-server[1326254]: Error decrypting message: error:0406506C:rsa routines:rsa_ossl_private_decrypt:data greater than mod len
Mar 01 17:30:59 game002 hashima-server[1326254]: Error decrypting message: error:04099079:rsa routines:RSA_padding_check_PKCS1_OAEP_mgf1:oaep decoding error

Could this be tied to the number of SpawnObject we can spawn in game? I'm experiencing the same crashes when I try to load stuff with SpawnObject in init.c (separate .c file but in init.c), after a certain number of lines loaded it just crashes with same Access Violation ... but when I reduce the number of SpawnObject lines loaded, it works just fine.

In T189290#2761163, @Firewalker wrote:

On Sakhal test, one of two airdrops completed successfully. I think this is why its hard to nail the problem down. Some airdrops are "randomly" working. But overall, if you disable them, your server should run.

Pretty sure this is up to the Expansion team to resolve, not BI

SCRIPT : 08:50:12.648 [EXPANSION DEBUG]: [ExpansionMissionEventAirdrop] Adjusted container weights:
SCRIPT : 08:50:12.648 [EXPANSION DEBUG]: ExpansionAirdropContainer_Basebuilding 374
SCRIPT : 08:50:12.648 [EXPANSION DEBUG]: ExpansionAirdropPlane::GetSpawnPoint - drop position <6390.000000, 0.000000, 8535.000000> - map is sakhal - size 15360 - center <7680.000000, 300.000000, 7680.000000>
SCRIPT : 08:50:12.648 [EXPANSION DEBUG]: ExpansionAirdropPlane::GetSpawnPoint - selected spawn point <15360.000000, 450.729736, 3352.719482>
SCRIPT : 08:50:22.666 [EXPANSION DEBUG]: [ExpansionMissionEventAirdrop] Adjusted container weights:
SCRIPT : 08:50:22.666 [EXPANSION DEBUG]: ExpansionAirdropContainer_Basebuilding 454
SCRIPT : 08:50:22.666 [EXPANSION DEBUG]: ExpansionAirdropPlane::GetSpawnPoint - drop position <845.000000, 0.000000, 11331.000000> - map is sakhal - size 15360 - center <7680.000000, 300.000000, 7680.000000>
SCRIPT : 08:50:22.666 [EXPANSION DEBUG]: ExpansionAirdropPlane::GetSpawnPoint - selected spawn point <15360.000000, 450.506683, 1024.718750>
SCRIPT : 08:57:06.771 [EXPANSION DEBUG]: ExpansionLootSpawner::Spawn - WARNING: Couldn't spawn ExpansionCamoBoxKit on ExpansionAirdropContainerBase<f2c07960>
SCRIPT : 08:57:06.771 [EXPANSION DEBUG]: ExpansionLootSpawner::Spawn - WARNING: Couldn't spawn ExpansionGunrack on ExpansionAirdropContainerBase<f2c07960>
SCRIPT : 08:57:06.771 [EXPANSION DEBUG]: ExpansionLootSpawner::Spawn - WARNING: Couldn't spawn CamoNet on ExpansionAirdropContainerBase<f2c07960>
SCRIPT : 08:57:06.771 [EXPANSION DEBUG]: ExpansionLootSpawner::Spawn - WARNING: Couldn't spawn LargeGasCanister on ExpansionAirdropContainerBase<f2c07960>
SCRIPT : 08:57:06.771 [EXPANSION LOG]: ExpansionAirdropContainerBase<f2c07960> InitAirdrop - total weight (kg) 337.746 - nominal fall speed 4.59436 m/s, wind impact strength 0.0734273
SCRIPT : [Permissions Manager] Admin (chicken) (76561197974270314) Successfully Logged in!
SCRIPT : 09:02:13.839 [EXPANSION DEBUG]: ExpansionLootSpawner::Spawn - WARNING: Couldn't spawn ExpansionGunrack on ExpansionAirdropContainerBase<34da10e0>
SCRIPT : 09:02:13.839 [EXPANSION LOG]: ExpansionAirdropContainerBase<34da10e0> InitAirdrop - total weight (kg) 375.568 - nominal fall speed 4.68892 m/s, wind impact strength 0.0718513

Exception code: C0000005 ACCESS_VIOLATION at 833EE1B4
Allocator: system
graphics: No
resolution: 160x120x32

From testing, it looks like moving the marker makes this reproduce faster

Игра вылетает на этапе входа в неё. Возникает ошибка (прилагаю отчёт и название). Так произошло после обновления.

I did this using scripted commands, but please consider modding of HumanCommandVehicle, especially allowing raise weapon (animgraph Raise). It can allow those feature implement even easier and for driver too.

And here you go. Only using Expansion Base Building Airdrops. Crashed on the third one.

On Sakhal test, one of two airdrops completed successfully. I think this is why its hard to nail the problem down. Some airdrops are "randomly" working. But overall, if you disable them, your server should run.

So far, my Chernarus and Sakhal servers crash the same, if Expansion Airdrops are running. Someone above said that Expansion team is discussing it on their Discord.

Same issues for us. Before this senseless update we didnt have crashes or crab like that. Update 1.27 happend, almost crashes on a hourly bases.
WIN-DC5QK4GAL09, 01.03 2025 10:56:06
Unhandled exception

I want my stuff back.

In T189207#2757802, @Bloodshot_vp wrote:

In T189207#2757700, @kuzyn wrote:

Update is out, slots are still broken.

You need to use the hotfix mentioned above.

In T189290#2760841, @Weyland wrote:

Disabled Airdrop in Expansion, server no longer crashes...nor player drops.

@Geez all back to normal now. Building works like before Update. Thx for the Support

you wont get your gear back, just re-loot, and that was your internet lagging thats what the problem was. next time you freeze like that log out

Please fix this issue, it's annoying

This also happened to me

Before, the server crash would display the relevant mod, but now it's not at all. I just experienced a server crash, which occurred when I joined the server. Before, the server had been running well and there were no players in it. I left for a while and then joined the server, resulting in a crash