@Geez I quit the game after this, just got back into it and again, killed by a cheater. I presume the game is still unplayable still then...
?

I took them

I have sent all crash reports via the send function.
This is the data as set above.
I just thought that someone could help me.

A fix to this issue is to delete the profile folder entirely in the "Mygames" folder.

It seems like setting it over all units using

@Geez ETA for fix please? (Been over half a year now since this report...)

Revision: 152543

Same issue for server hosted locally in South Africa.
Connecting to the server I have 5ms, in the browser it has 350ms.

Latest experimental version.

Can confirm this result as accurate and reoccuring whenever a road part object is selected/moved from within TB buldozer.

It seemed random, but I didn´t pay attention to what my friend was doing atm. Could be T187337 related.

This has been resolved for 1.27. apparently

Reason: Access violation. Illegal read by 0x7ff68a36f707 at 0xffffffffffffffff

Mi usario es El Thomas243

please devs i cant stand these players building only an armoury at simons wood and then not building anything else

this is a weird and quite old bug.
if u actually CRAFT the fireplace and place it, and then built the stoneoven - all slots can be used on it.

https://streamable.com/1f96c7

My game does this to and I'm running a 3060 Ti

Local Host issue may relate to T187337 and T187928 seeing as I was the host in my case aswell.

Saw the very same server was back up again, so I tried replicating it the same way but was unable to.
Possible you need to have more vehicles or a bit more progressed / filled server for it to happen.

In T187719#2731087, @lwing wrote:

In T187719#2730416, @byNautiic wrote:

I've experienced this a few times on Xbox Series X too.
Was only when using Soviet radio backpack though.
HyperX Cloud 3 headset, just in case it shows to matter.

This happens with any comms in game including local voice chat. If you are mistaken and think I am refering to being able to hear myself talking then that is not the bug -- I only have the radio tuned to the same channel twice because it lets me demo the problem by being able to hear myself talk. You may have heard yourself twice while wearing the backpack because you had two radios and thus tuned to the same channel (which is not a bug)

Could it be related to T187337 ?

In T187719#2730416, @byNautiic wrote:

I've experienced this a few times on Xbox Series X too.
Was only when using Soviet radio backpack though.
HyperX Cloud 3 headset, just in case it shows to matter.

Seems to be corrected in version 1.2.1.169. This ticket should be closed. Sadly, doesn't work with custom maps. I'll file a new ticket for this one.

Yes haven't been able to play DayZ since Dec. 23rd. I've done everything from deleting config files and turning off the cloud on steam to full uninstall delete all files and then clean install. Nothing seems to work, and it's only DayZ all my other games run fine. To answer the corrupt files question, I don't know. How can I see what's all corrupt and what's not?

Hello, that's awesome!
Hopefully it worked.

No mods!

https://youtu.be/LHkOqsdyypQ?t=1167&si=uaA4v2_KcJ-Bvo32

https://youtu.be/LHkOqsdyypQ?t=895&si=CByfk46BJFt-DvoX

0xC0000005 - STATUS_ACCESS_VIOLATION

In case anyone encounters this in the future - the fix is to lower video settings in game. I can't remember the exact changes I made, but I clicked 'default' to restore default settings, then lowered antialiasing and another setting (I think the one above or below antialiasing in the menu). This got it to work.

Same thing in Experimental 1.3.0.25

I see

@Leopard20 could this be something to do with my hardware ?

This report includes files that may contain personal information. For more information about how we process your personal data, please visit
https://www.bohemia.net/privacy-policy.

This report includes files that may contain personal information. For more information about how we process your personal data, please visit
https://www.bohemia.net/privacy-policy.

I think there's something wrong with the camera

The only thing I saw was that he killed you weird, he didn't aim at you, he just shot you in the side.