- User Since
- Apr 28 2018, 6:41 PM (281 w, 6 d)
Jun 14 2020
Jun 10 2020
Seems to be fixed in 1.08.153164.
Jun 6 2020
Jun 5 2020
Jun 4 2020
Nov 21 2019
This seems to be related to T146463.
Sep 22 2019
Aug 21 2019
Aug 19 2019
Hello. This happened to me as well tonight with a the KA-M. Relogging fixed the issue.
Aug 18 2019
This also occurs:
- with other guns (tried it with the MK II and the FX-45)
- if you go prone during the reload animation
I can confirm that the same thing occurs at a corner bar in Novodmitrovsk. You also can't open the back door of the building.
Aug 17 2019
Aug 15 2019
Jul 19 2019
Jun 25 2019
Jun 22 2019
May 21 2019
Can confirm this on 1.03.151544.
May 11 2019
I found my first Gunter 2 just now.
I can't get the bandanas to work in 1.03.151457 either. It works in 1.02.
May 10 2019
Apr 4 2019
In my types.xml, in the server files directly from Steam, the "Mag_FAL_20Rnd" has <quantmin>10</quantmin> and <quantmax>70</quantmax>.
Mar 31 2019
The keybinding screen is definitely bugged and has been so in all the 1.02 Experimental builds in my experience.
Mar 30 2019
Mar 26 2019
Mar 25 2019
Feb 19 2019
Ah yes, it's just the up arrow missing.
Dec 16 2018
Oct 24 2018
I can add to this. I experienced movement bugs after using the F5 key on stress test #52 (SWE2-1 and SWE2-2, 0.63.149189). I deleted the contents in my DayZ folder and the problem persisted.
- Pressing F5 and then pressing it again before the lying down animation finishes causes the player character's movement to become bugged. The player character rubberbands and moves really slow when jogging, whereas the character moves at jogging speed when crawling.
- Pressing F5 again and letting the animation finish resets the movement to normal.
I think that's the exact issue. I tried reproducing it on stress test #52. The duct tape isn't infinite after all - the percentage is only reduced by 1 percentage point for each improvised suppressor. It also seems to be occurring no matter whether the duct tape is on the floor or in the player inventory.
Oct 20 2018
Sep 5 2018
I've experienced this as well for quite some time on the PC version. For me it usually happens at medium distance (approx. 150 meters) and the entire hunting stand comes into view when I get closer. I'm running 1080p at pretty low settings. I took a few screenshots on stress test #44.
Jun 29 2018
I’ve experienced the same issue persistently in the 0.63 offline mode (see T129166), in the stress tests and the experimental version.
Jun 21 2018
Logged on SWE 2-1 a few minutes later. Played for about 2 minutes before I was kicked off again with the same message from BattleEye.
Jun 16 2018
I've also just experienced that (reported under T130377)
This happened again on Stress Test #25 (0.63.147256) on SWE 2-2. On a path near my spawn I found several stones, each displayed as 8/8 although they were single stones.
Jun 5 2018
I had the EXACT same problem on the SWE 1-1 server (reported under a different ticket). Couldn't interact, no countdown timer when logging out, couldn't connect and got the character locked on other servers.
May 28 2018
Seems to be fixed now. I don't experience this issue anymore in the latest offline build, version 0.63.146951.
May 23 2018
Also happens at the guardhouse near the harbor in Elektro.
May 19 2018
May 11 2018
The same thing has happened to me on the bus on the shore near Skalisty. The exact same spot in the bus. I suspect it's the current "auto-vault" that causes this.
May 10 2018
I managed to find a burlap sack during stress test #6, but strangely didn't get the option to put it over my head even though I held it in my hands. So I couldn't test it online.
Good point! I must have.
I had a chance to try it today during stress test #6 and did not experience this issue online.
I can add a few. Seems like the new rocks are of a different size than the old ones.
I experienced the same. I had the burlap sack in my hands and no empty spots in my inventory. Putting it over my head and removing it made the sack disappear.
May 5 2018
May 4 2018
I tested it yesterday in version 0.63.14661 and the issue still persists.