July 17th 10:20pm Uk time I play on Xbox and this has started happening to me tried everything can’t join any server

yes, i have read your response but it didnt help and i also recently upgraded my gpu, it also didnt help

100% fully agree with this. Something the devs need to look into. Unfortunately you’ll probably be ignored.

Resolved for 1.2.0.76 and higher.

One more thing I noticed. It spawned me about 100 yards from where I died. That's never happened to me before.

This helped, no more error, but it lauches and automatically shuts down after 1-2 seconds. Do you know what could cause that?

Thank you, we will investigate with BattlEye.

Also tried
marker_0, marker_1

dedmen did it

should be fixed in nect update

should be fixed with next data

should be fix in next data

Hello again. Have you opened dayz through Steam after updating the tools?

Hello. Yes I do. Do I better use experimental untill the fix or the problem with stable workbench is on my side?

In T182110#2624663, @lankercool wrote:

This was not done by design, it is presumed to be done by design by the BI Wiki Editor, don't misconstrue.
It either way does not make much sense to change this value only when revive is enabled, as it would largely cause the Medkit(and the medic trait) to lose about half its effectiveness on the field which is being able to full-heal units.

looks like requester module has default values preset in GUI

was fixed in march 22

Hello MilesDownshur.
It looks like you are trying to run the Workbench from DayZ Tools for Stable. Do you have the DayZ Experimental Tools installed?

Here is some video

look like typos, as xxxtext is already used, try after data update plz

Hello patriaminas.
According to the devs this is not going to be addressed currently.

In T182899#2639071, @Akidan wrote:

The game still gives me the same issues, even after a fresh install of OS, Steam and DayZ..

Would you suggest going back to Win 10?

In T182735#2639152, @darkenedlotusdrake wrote:

is there any way to fix this issue?

Hello ScorXpion.
Can you please describe the crash in greater detail? Was this one time occurrence or has occurred multiple times(always?)? Upon which circumstances does the crash occur?

Is this being fixed?

Has this not been fixed yet?

is there any way to fix this issue?

The errors listed should be fixed in next data update, any more?

One of thing i tried to talk about in my overly long post above is the connection between the character in the game and the player as the controller. How i as a player act and how my character reacts are different. We as players are not military personal. Some of us are, and some of us were, but i will make a large assumption in saying that 'most' of us are not. We vary in age, abilities, skills, language, culture, and even control method or platform. How we as a player react and the choices we make dictate the experience of our character in the game.
Our character experiences all the consequences we as a player give them, both good and bad. How we value that character is largely up to us, much like how in DayZ we can choose how that character progresses by the actions we choose. We can choose to play as a Soldier or as close as we can, or we can jump in a chopper with an Australian who is blaring AC/DC and doesn't seem to value his life (or ours) in the slightest. We can watch in horror, or in hilarity as he loudly states "is that an enemy choppa? I'm going to ram him!".
Or we can join a mil sim server where everyone has a rank, they intend to play the game in that way, and they have built the server with mods tailored to exactly the experience they as a collective want.
There is no wrong answer. Arma gives you the freedom to experience it how you want.
The balance is between the freedom of the player and the limits set to the character.

hello?

Someone please help figure out which way to dig......

The game still gives me the same issues, even after a fresh install of OS, Steam and DayZ..

Works in 2.18.

In T182498#2638929, @Geez wrote:

We do not believe the fact .mdmp was not created was caused by the exe being renamed. However it makes it much harder for the devs to analyse the issue if the executable is renamed.

It looks like when digits are imported to the workbench and converted to ANM it uses Truncate instead of Round. And that causes a loss of information.

@Khaosmatic
The developers should aim to create engaging gameplay while still capturing elements of real-world combat.

Hello dlusive.
There is no issue at the moment, seems there are not enough players playing these modes.

This is still an issue in 2.16.

As far as I can tell, this is no longer an issue, the actions don't reset the fire mode.

I encountered the same problem, I fixed it by deleting the game settings in my profile

I guess also close T181159: [Exp] Low Ready not functioning then

Hello GlutenFreeVapes.
Currently there are no plans to address this.
Regards,
Geez

Hello Aragon.
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

Other issues should be fixed in next dev

Hello Akidan.
We suggest to remove the launch parameters as most of them are obsolete and do not have any effect, especially USEALLAVAILABLECORES, -cpuCount=6 -exThreads=12, they can in fact cause problems instead.

Hello lipekso. We will investigate with BattlEye.
Regards,
Geez

Hello Flynnruk.
We have tested this extensively but we were unable to reproduce the issue on our end.
Regards,
Geez

We do not believe the fact .mdmp was not created was caused by the exe being renamed. However it makes it much harder for the devs to analyse the issue if the executable is renamed.

Applying forced suppression screen effects and control effects is a cheap method to fundamentally apply a bandaid on a problem which is solved if you disable respawns or make dying actually a threat to a players gameplay experience. Would it work for quick session, rapid gameplay like conflict? Yes for sure. If you actually want this to be impactful and you are playing "MILSIM", turn off your respawns and see how that changes up the way players take part in a session. If they genuinely care about the experience of both themselves and those around them, they'll start working hard to not die and things like suppression will then just work even moreso than it already does, without forcing game-y filters over the player.

In T182498#2638413, @Geez wrote:

We would also suggest to not rename the server executable

Please deal with these guys. They are making the game unenjoyable