take it off and put it back on usually fixes it

Update: This bug appears to effect all helmets, upon further inspection.

I'm seeing this also, I have a private server just to try out new features, and the car positions seem to be messed up. I had a couple spawns where the car was sitting on its roof upside down, and some where the car was sitting about half on a pile of debris or on another static car, and many of the parts were ruined (even though untouched by other players). And the cars I've got running there is no longer an option to turn on headlights. Also you cannot remove parts like battery, radiator, sparkplug, headlight bulbs properly, you have to walk around the car at random spots and hope that you get the option to remove the part, it does not seem to have anything to do with being in proximity of the part you're trying to remove.

Still assigned to: none

@Geez just found out it's now can be enabled using L key, please close the ticket!

i can confirm that using DayZ_BE.exe fixes the problem. i thank you for your time and help.

Hello Geez,

In T139528#1869590, @Geez wrote:

Hello AXEL7.
Fraps is not supported any more and should be used only at own risk. Unfortunately there is nothing we can do about the crashes related to use of FRAPS with the game.
Regards,
Geez

Hello Gremmie and thank you for the report.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

Hello AXEL7.
Fraps is not supported any more and should be used only at own risk. Unfortunately there is nothing we can do about the crashes related to use of FRAPS with the game.
Regards,
Geez

Hello everyone.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

Hello stretchmatthew.
We are going to analyse the crash dump files you have provided and will let you know once we have more information regarding to the issue.
As for the other reports you mention - we have checked the previously posted tickets by you, all of the tickets have been responded to and we required additional information from you, which you did not provide.

hello nelis1846.
If you use the DayZ_BE.exe executable instead of the DayZ_x64.exe, do you experience the issue as well? As the DayZ_x64.exe launches the game without BattlEye client, and when you would attempt to connect to a server with BattlEye enabled, this would result in the game restarting with the client running.
Also, you can switch off BattlEye on the server with the following parameter in the server configuration file

Now we have another issue with the Olga 24. I posted a thread here but it seems to be ignored. This bug will always persist :/

I have the same issue. The personal proximity light keeps getting enabled while in NVG view and I in turn keep toggling NVGs in order to disable the light. This should be a high priority fix imo.

Yes, it works properly in the latest stable and experimental patches. But oil is still useless and power supply doesn't have any model while attached to olga 24.

Enable nvg and listen for swearwords from temmate about being blind RFLOL

Hello Geez,

Hello everyone, is this still an issue on the latest stable / experimental version?
Regards,
Geez

Hello anonymous.gr and Deranged.
If you switch to the experimental version now, does the issue still occur?
Regards,
Geez

@Geez hi.
Maybe close this ticket?

I think the nature of this problem applies not only to the battery. I do not know what to associate with this problem, but today I had the same case with the keys to handcuffs. I entered the game and when I first opened my inventory, the image of the keys was correct. At some point, I received the same result as in the ticket - there was no picture of the keys to the handcuffs. I suppose that this can happen with any object in a slot for one cell.

Server Specs:
Dell R710 with 2x X5660
6 cores allocated for this instance
12GB Allocated for this instance
Running off an SSD

Looks like it's fixed.

Looks like this has been implemented in 1.03, cool.

This needs to be fixed ASAP!

Fixed in 1.03.

Confirm the but bug but have not observed the difference between un-planned and planned reboots.

Gates have gotten worse. After reboot you still have to cut off your lock and rebuild the gate to put on a new lock....but now in addition to these existing issues as mentioned you are blocked after opening the gate and can't walk through. My work around is to open the gate and then close it on my self so I'm facing the inside of gate, dismantle the upper or lower boards and then run forward. This pushes me through the gate to the outside. After this I can open the gate a walk through just fine. Have to reassemble the gate afterwards...running through tools.

I will support the problem, I noticed that the problem will appear with random reboots, but not with the planned ones, after the planned reboot it works stably, there is no possibility to pass through the gate until it interacts, namely add / remove building materials.
as well as there is a problem with the locks after the reboot, the password becomes random.

it is posted Feb 14 2019, 8:34 PM
Devs, why this don't fixed?

@strelok12 I see on your video that when a black screen appears, a low FPS appears at the same time and the sound disappears. As soon as the sight is lowered, the screen, FPS and sound are restored. I do not know if this is connected with the server or your PC, but I would start by checking the game files and defragmenting them. How often does this happen? And how at this moment your RAM is loaded, how many percent is free / not used?

Correction, apparently it doesn't have to pertain to attachments. Restarted the server now and the bug remained even though all attachments were removed.

Correction, apparently it doesn't necessarily pertain to attachments. Restarted the server now and the bug remained even though all attachments were removed.

After some experimenting, I can confirm that this bug seems to pertain to various attachments to the gate. If you leave any construction materials attached to the gate, you will get the impasse bug; remove all nails, planks, sheet metal, etc, and you should be able to use the gate normally. However, this still needs a hotfix, because this has also made things like barbed wire unusable as it also counts as attatchments.

Just happened to me too... (Worse on 1.02).
Devs should look at it seriously.

@Geez The problem was partially solved. But there are still frequent problems when we get visual contact with the object and its state, but we don’t see it in the vicinity menu.
https://youtu.be/vlVe0WsEUsU

I tested it even on an exp server, same problem: https://feedback.bistudio.com/T139503

After some experimenting, I can confirm that this bug pertains to various attachments to the gate. If you leave any construction materials attached to the gate, you will get the impasse bug; remove all nails, planks, sheet metal, etc, and you should be able to use the gate normally. However, this still needs a hotfix, because this has also made things like barbed wire unusable as it also counts as attatchments.

In T138735#1868644, @Vitdom wrote:

I'm also getting this issue when I emptied my found Mag_FNX45_15Rnd with 5 rounds. The problem is, unlike for you, my rounds didn't end up in any medical kits or other containers nor on the ground... I noted that at the same time, other items on the ground in the vicinity didn't show up on the Inventory screen, but further away other items did.
Experimental Version 1.03.151529

@wriley I agree, this happens often, because everyone calls his problem differently and we do not have a separation of problems by content category. I usually do not try to search for the name of the problem, I search by the name of the content with which the problem occurs. This reduces the chance of getting past the existing tickets. In your ticket name, the keyword is "hot bar", and in the problem description the key element is "in the slot \ or slots". If you search for tickets by "slots", you are closer to a successful search. I also had duplicates. You can close the ticket yourself through - Edit Related Tasks ... Close As Duplicate.

Bah, still bugged.

Happened to me many times. I even had the impression it became worse with 1.02. I always had the feeling that it randomly happened when I logged in with my weapon already in the hand, instead of inventory. However, on one moment this bug appeared as well when I logged it while my weapon was initially in the inventory.