Same thing on Livonia experimental, 2-3 tries before can get on the serv

Spawn points restrictions are need to be fixed, not this. When you fight solo against 3ppl party, kill 2 of them, fighting with 3rd and by that time (less than 5min from the beginning of the fight) 2 of his dead buddies are already managed to get back and loot their dead bodies. Profession spawn presets are good for custom servers, can outplay it very nice if you have some custom global story on your serv and probably some special missions for some of those classes, but vanilla at this aspect in currents state is OK. You spawn with low tier clothes, no food, one bandage, how you gonna survive? - it's your problem, go build your own story.

Check the integrity of game files via steam, If those are OK than it's not game problem, most likely your sound card/driver or both.

Yea you kinda said it yourself, players will just respawn until they spawn with whatever gear is the best. The thing is, this would be great for an RP server or whatever, but the vast majority of DayZ players would simply just dig for that initial advantage, there would be specific spawn kits which would just be better than others, and then everyone would go for those ones and suicide if they got anything else.

I've seen this on modded servers. Interesting, however getting new clothes is also part of game's progression. Starting with hunter gear seems like a massive shortcut to me. In short. I like the way things are at the moment. Well balanced and equal starting point for all players...

Duplicate of https://feedback.bistudio.com/T175482

When this happens while in a firefight, you will see that hits stop registering just before getting the kick. So I guess the game thinks it's an unstable connection, but it's only unstable within the game's ability to process the data. Whether on the TX or RX side (or both), I have no idea. Also, I've had this happen so many times where I'm the only one on the server.

Same thing with COT and m79+40mm. When spawn 40mm ammo via COT M79 won't load them into the chamber, they will go back into inventory or fall to the ground. On the other hand naturally spawned 40mm grenades works perfectly.

I see this Kicked for ""Unstable Connection"" when playing on an official - no mods server about 37km from me

I should also add that setting max ping to an insane number doesn't help, nor does setting the speed hack detection level in the config.

Interesting...Well, thanks for spending the time to look into it Geez and crew and relaying that info.

What I mean is how can I tell if a mod is causing the issue, and ideally pinpoint which mod. If I'm going to open a bug report with mod author, would be helpful to determine which mod is causing it.

Additionally, there is no scale point on the left edge to reduce the window size. Only the right window edge can be used to rescale.

Thanks Geez. Can you tell me how you are determining that from the information provided? I'd like to be able to interpret these myself if possible.

yes, I was able to get it to work after restarting steam, this has happen almost daily since the update.

Hello Armor.
This will be fixed with the 1.22 hotfix number two!

Thank you.
It appears like the crashes are caused by some mod and unfortunately there is nothing we can do as the issue has to be fixed by the mod creator.
Regards?
Geez

Thank you, we will investigate with BattlEye.

Hello Nate_LapT.
The conditions for that message to appear are just steam being offline. Do you have Steam running and up to date?

Hello everyone.
We only have been able to confirm this only when using some sort of admin tool mod(Such as COT). When spawning the grenades with these, it does not spawn full quantity of Ammo_40mm. This is why it is possible to combine them and then they explode.
This is not possible with grenades that spawn the regular way.

In T175433#2498695, @Geez wrote:

Thank you, we will investigate with BattlEye.

Thank you very much sir, it's my mod so I've fixed it as follows (see below) and I'll keep track of the changes.
Anyway, we have had the mod on serever for half a year now and it has never been a problem.
Whether this will help the crashes or not, thanks for the message.
Have a nice day.

In T175429#2499276, @5treet wrote:

Hello,
I found a mod that registers the object animation in PlayerBase, as you mention, so is this a problem? Is it possible that the crashes are caused by this? We never had crashes in <LOAD EXISTING CHAR> <RESPAWN NEW CHAR> before 1.22 HOTFIX 1 from BI. And we use this item before 1.22, is possible to crash apear right now?

modded class PlayerBase extends ManBase
{
    override void Init()
    {
        if ( !GetGame().IsServer() || !GetGame().IsMultiplayer() )
        {
            DayzPlayerItemBehaviorCfg fireArmsItemBehaviour = new DayzPlayerItemBehaviorCfg;
            fireArmsItemBehaviour.SetFirearms();
			
	    DayzPlayerItemBehaviorCfg     toolsOneHanded = new DayzPlayerItemBehaviorCfg;
            toolsOneHanded.SetToolsOneHanded();

            DayzPlayerItemBehaviorCfg     twoHanded = new DayzPlayerItemBehaviorCfg;
            twoHanded.SetTwoHanded();

	    GetDayZPlayerType().AddItemInHandsProfileIK("Custom_Item_apple", "dz/anims/workspaces/player/player_main/player_main_1h.asi", toolsOneHanded, "dz/anims/anm/player/ik/gear/apple.anm");

	}
        super.Init();
    }
}

In T175429#2499255, @Moonny wrote:

I can tell this might but not must be releated to how items animations are registered in some mods. If they are registered in PlayerBase class - expect LOAD EXISTING CHAR crashes, because such registration was a workaround years ago and some modmakers here and there sometimes take this as a reference.

Those barns in particular are really known for that. The spawn points needs adjusted upwards just slightly

Mmmm Ghost bullets.

Ok I figured out (seems like). We can apply bitwise operations to constants like here

I can tell this might but not must be releated to how items animations are registered in some mods. If they are registered in PlayerBase class - expect LOAD EXISTING CHAR crashes, because such registration was a workaround years ago and some modmakers here and there sometimes take this as a reference.

thanks, that works . .. . .

https://clipchamp.com/watch/SxzP6OdzSOn here is another clip of the issue on another server

https://studio.youtube.com/video/ZBt2X0FMd2U/edit another clip of reproducing it

https://www.youtube.com/watch?v=g_23tPmBbaU here is a clip of me testing it on a 40 pop server

https://www.youtube.com/watch?v=Hrrl2k4ckkM this is a link from a player who had the issue

Had this happen a lot of times this patch... at least 5 times. I can't figure out what's causing it.. perhaps a server restart bugs weapons that have an "automatic" setting ? I logged off with an M70 in my hands and once I logged in, it was still in my hands, and I swapped to AK and it started blasting the moment i raised the weapon.. ( happened also wih AUG, famas, and m4 )

Ok, that didn't take long. I was playing on a server today (where I encountered this issue before) - I then closed the game and restarted it about an hour later. I updated all mods prior to joining. Received the same Status Access Violation as before. The crash report is attached.

This also applies to ActionPourLiquid.

legend <3

So is this some function or code in some mod and crashes the server when it runs this function?
I understand you don't have more information and thank you for that information as well, but we just need to know what HeadingModel is, if it is code in some mod that we could look for, or what it actually is.
Thank you for your time.

In T175429#2498878, @5treet wrote:

Hello,
thank you for trying to find some leads.
Is it possible to at least give us a little more information about HeadingModel?
If it changed after the update to 1.22 or 1.22 HOTFIX 1 ?
Or something a little more specific so we know which mod to focus on, roughly what to remove, or who to contact next?
Any clue as to what HeadingModel is in charge of, or what it handles, anything we can pick up on further.

Thank you for your time and have a good day.

Resolved for hotfix number 2 of the 1.22 update.

Hello,
thank you for trying to find some leads.
Is it possible to at least give us a little more information about HeadingModel?
If it changed after the update to 1.22 or 1.22 HOTFIX 1 ?
Or something a little more specific so we know which mod to focus on, roughly what to remove, or who to contact next?
Any clue as to what HeadingModel is in charge of, or what it handles, anything we can pick up on further.

Hi Geez, thanks for the reply. It tends to happen at random on the few servers I play on. So, no it is not always the same server - I can think of three different servers (at different times) off the top of my head. I can send more crash dumps, but I believe I've recently purged my logs so I will need to wait until it happens again.

Hello mnkybtlr.
Does this always occur on the same servers or does this happen across various servers? And would you be able to send more crash dumps? Either way so far it seems it is related to modded content (missing mods on your end)

Hello PhatmanPizzle.
The issue appears to be related to the mods you are running. This might be either an issue with the mod itself which has to be fixed by the mod creator, or the mod is corrupted.
We suggest that you try to uninstall/unsubscribe all your mods, then verify the game data and re-download the mods again. If the issue still persists upon doing so, then it is very likely an issue within the mod itself.
Regards,
Geez

Hello Half.
This appears to be caused by some mod you are running. Unfortunately we cannot tell which mod is it besides that it crashes on HeadingModel.
The mod creator will have to fix the problem on their end.

Hello again.
This appears to be caused by some mod you are running. Unfortunately we cannot tell which mod is it besides that it crashes on HeadingModel.
The mod creator will have to fix the problem on their end.

xD
its ok, we will wait next 4 years

In T175275#2498772, @Geez wrote:

In T175275#2498594, @Norealname wrote:

@Geez
verifySignatures = 0;
breaks the queue, tested on a completely vanilla server

Also we are aware of this issue and it is scheduled for a fix. However putting zero is not recommended by us generally as this allows people with outdated mods/mods not installed on the server/without mods to connect to the server. which can cause issues.

Thank you so much for helping me, we are really helpless.
Here I send all .mdmp from all crashes.