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.

This amphibious pathfinding issue seems particularly tricky! Three angles to investigate:

1. Test collision meshes using BlockBlast physics visualization tools to detect underwater anomalies
2. Analyze AI decision trees with HappyGlass neural network mapping interface
3. Compare buoyancy parameters against ColorBox amphibious vehicle template library

Would logging the propulsion system's torque output during water transitions help identify if it's an engine limitation? The bubble animation vs zero speed discrepancy suggests conflicting state triggers.

@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

Please fix asap !

Can confirm. I just tested with only CF and VPPadmintools and plants get stuck in whatever growth stage they were in prior to the restart.

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

The issue seems related to my script-spawned vehicles being added as a child node of the spawner entity (so CE can track removal and enable spawning at that point again).

I started having issues as well after the 1.27 update. My symptoms are the access violation. As well, when this happens, players report no longer being able to join without crashing to the access violation error. What is interesting is I removed all mods from my server one by one to see if any one specific mod caused the issue, down to the point that it was just the Deer Isle map. It did not restore my ability to log back in. However, if I wipe the playerdb file and let players rejoin, it seems to behave fine for a short period of time. Upon slowly reintroducing mods, it seems to inevitably happen again. I would have anticipated the playerdb file updating as mods are removed and items are no longer in inventory but it's almost acting as if the playerdb is becoming corrupt. Most players state it works for a while and inevitably freezes and happens again. This happens to me on linux or on windows servers, as I am able to take the known broken playerdb, move it to my other server, and reproduce the issue, even with different mods.

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

I was having very consistent crashes with an air drop mod. After removing that mod, the crashes now seem to be random. However, I'm starting to notice player connect/disconnect activity at the end of the all my script logs on crashes. I've seen a similar issue with a vehicle mod roughly a year and half ago. When a player joined or died and respawned as a certain character type it would crash the server. Were any changes made to characters players can play as?

Easiest way to fix it would be to add some dummy-void sound in played audio files, to mimic silence while the sound would still play.

It would be good if the sound was 3times less frequent.
The surfacemaks responsible for this noise is not so common, sound is nice and it would be good if it wasn't so frequent.

I cant log in. I dropped a pair of boots to another player and cant log that player in to pick them up.

I was playing on server 4268, it glitched when I was killing zombies.
I was on top of a sand bag attacking downwards. The zombies couldn't hit me, then the glitch started. I no longer could hit the zombies. The axe just went through them without connecting.
A few minutes later, my player started receiving hits from the zombies, however, I was still on top of the sandbags and no zombies were near me

I was playing on server 4268, it glitched when I was killing zombies.
I was on top of a sand bag attacking downwards. The zombies couldn't hit me, then the glitch started. I no longer could hit the zombies. The axe just went through them without connecting.
A few minutes later, my player started receiving hits from the zombies, however, I was still on top of the sandbags and no zombies were near me

Yes. your logs basically look like mine. Must be the same issue. For me it crashes very quick. Can’t really play multiplayer. I get kitted and dropped at the front line. Then it freezes for a second or 2 and the windows pops up. I struggle with it since weeks and I tried every experimental version since then. Only thing that worked was deleting the ReforgerEngineSettings or how it was called. It didn’t crash for an hour after that but when it crashed it got more regular again.

I have the same problem, but my Server is now restarting all 15 Minutes.

Same challenge here. Thx for the hint. Will check next time and keep you posted. Any plans or timeline when you will fix this?

Hello, the same problem

Same here... can be combined with: https://feedback.bistudio.com/T187941

Mon pseudo dayz est aS3RTEa

Thx

In T187294#2725187, @kawalec wrote:

@Technicolourmatador
Even now, when defending base is so easy, very few people spawn on attacked bases.
90% of players don't like driving, don't care about driving, don't know how to do it. So they don't drive to attacked bases.
99,99% of players love flying and can't do it.
So if you sum this up, for most player it will change the game into 30-minute long fight with AI and then loosing/wining without even experiencing any highlight of Conflict.
Why? Because a team of 2-4 people with Willys can drive around every enemy base and capture one by one. Not to mention heli.
In the first week over 50000 copies of PS version were sold. It marks a huge change for Reforger and Arma franchise. We're just stepping out of dark burrow of very niche game into the wast world of casual players.
Such mechanics as this new one may be too hardcore for them. They will still be playing the game, but they will be purposefully omitting it's core features. Exactly as it happens now with supplies, spawning AIs, making self-defensive layouts of bases, using radio spawns, proper communication etc. I'm not even mentioning teamwork, because at the moment it's nearly non-existent.
I can manage with any new mechanics, you can also and many other more experienced players. But I'm worried that such changes may slowly kill the idea of Conflict.

In T187294#2725495, @byNautiic wrote:

Well, we won't be dealing with this:

That was the best decision to turn off this function. I was tired of fighting the Freshspaws with spawn protection. If you don't defend your base, you're out of luck. Fair play for all. Spawning on bases that are under conquest is unfair! I don't need opponents spawning in front or behind me and happily killing me. And I have to guess when to fire. Yes! They have protection running. THAT is unfair. PLE
ASE KEEP THAT IN BI.

I tried Debian 11 in a podman container, that didn't make a difference.

I no longer have the logs unfortunately. But if I remember correctly it was a migration from debian 11 to fedora server 39. I know this is not useful for you without logs.

Im having these issues as well, i assume no one has a fix yet? Is it tied to the recent update pushed a coupel days ago?