After 1.28 update, I had a player report invisible walls at the cave that I built. I went to go investigate it. I noticed inside and outside there were nvisible walls and the hit box on some of the walls also had issues as well. Reported as many others did too. Hopefully it can be fixed soon.

I've been planning to switch to AMD for a while now.. has this been fixed? or going to be?

Same here

I have same problem even without deletions. Before patch 1.28 all was good. But now we have not working mapping (with invisible walls) + ugly car physics. I understand that you have new baby - Arma Reforger, but we never receive enough love as very big DayZ community. Please send us love. If you can't, just back car physics(that's better in every game I know) + fix this mapping bug. And you can stop updating have, we have enough mechanics, all was good on 1.26/1.27. We have mods and all good. Thanks. Have a good day, Human.

I can confirm that I am experiencing this issue on my end aswell.

Revision: 153035

Major issue on my server, and quite a few other server's I've heard from

There are some indirect approaches via character command handler to force weapon fire:

//------------------------------------------------------------------------------------------------
modded class SCR_CharacterCommandHandlerComponent : CharacterCommandHandlerComponent
{
	protected bool m_bACE_ForceWeaponFire = false;
	
	//------------------------------------------------------------------------------------------------
	override bool HandleWeaponFire(CharacterInputContext pInputCtx, float pDt, int pCurrentCommandID)
	{
		if (m_bACE_ForceWeaponFire)
		{
			if (pInputCtx.WeaponIsRaised())
				pInputCtx.SetWeaponPullTrigger(true);
				
			m_bACE_ForceWeaponFire = false;
		}
		
		return HandleWeaponFireDefault(pInputCtx, pDt, pCurrentCommandID);
	}
	
	//------------------------------------------------------------------------------------------------
	void ACE_SetCanHandleWeaponFire(bool canHandle)
	{
		m_bACE_CanHandleWeaponFire = canHandle;
	}
	
	//------------------------------------------------------------------------------------------------
	void ACE_ForceWeaponFire()
	{
		m_bACE_ForceWeaponFire = true;
	}
}

However, this approach does not work when the weapon is lowered, so it's not good for features like weapon cook-off.

Hey Geez,

Thats why I am asking for the *exact* repro, so I can recreate it on my side

Confirmed! Seems to be working now! (profiling 2.20.153025)

Seems to be fixed in profiling 2.20.153025!

Seems to be also fixed in Revision: 152992

Is a fix for this coming? Or any status updates?

и ещё где папка с документами

что значит запустить стандартную версию,это где"?

Resolved for one of the future updates

Hello, do you have any custom spawns or increased numbers of AI? If so, then we would suggest reverting them.
Regards,
Geez

Hello,
this is caused by the modded content you are running.
We would suggest removing all the mods, deleting your DayZ documents folder and then verify the game data.
Once done, launch the vanilla version and if it works without issues, load mods and try to connect again.
Regards,
Geez

Turns out there is already a ticket for it: T166418

Also still a thing in Reforger, but typedef can be used as a workaround:

ProvokeTypenameIssue(TIntArray) //no problem

Hello,
The server crashes or your client crashes or freezes?

I understand. Thank you. I've been playing Dayz for about a month and didn't know there were any system messages on the servers and how to open them.

Am also having this issue.

постоянно вылетает с ошибкой ' выход из дейз произошел необычным способом

This crash occured twice, so I've uploaded both reports. Also, I noticed my video settings had changed yesterday before this crash, and I had to reset them manually.

Resolved for 1.29

Resolved for 1.29

Same issue happened to me on a couple of official servers, so had to play community.

Hello
The crash dump points towards nvppex.dll file, indicating a problem with your GPU drivers. Please do a clean installation and check your OS for any corrupted installations/files. Also make sure your system is up to date.
Disabling HWAA in the game might resolve the issue but the root cause is somewhere on your system.
There is also a chance that if you are running Nvidia app instead of Ge-force experience that that is the cause of the problem.
Regards,
Geez

Hello,
The crash dump points towards the following: format = 0x00007ff709f42120 "Unable to locate a running instance of Steam"

Could you try to invite someone into a team and then leave the team? This could potentially fix the issue

Thank you for the report.
All hacking incidents are being investigated by BattlEye.
Regards,
Geez