Epic: https://feedback.bistudio.com/T159206

Lets add the old man his reaction too, couse he will probably forget

Can we please add

Kcmav123

TheRunningManZ

sanguine00

To this ticket?

Thanks

sanguine00 gave this analysis on the epic

The ADS bug appears to be a desync where the server recognizes the command, but your client does not. This is why if you get the bug you will also be forced to move slowly - the server is correcting your movement speed to be what it would be if you were *actually* ADS-ing.

Tap again and the server "lowers" your gun and you can once again move normally.

Tap a third time and finally you are ADS on both client and server.

The bug does seem to occur most often when attempting to ADS (or raise your weapon) while transitioning from different stances.

I've cleared my diary @Geez, let's dance

More observations incoming... caller please hold

Hi GeeZ,
I have something similar happen to me when meleing zombies which I think could be connected.
It seems to have the same properties.

I assumed it was me doing the steps wrong, but the more I practice, the more I see it happening inconsistantly.

To reproduce:

• Hold a sharp item that can complete a sneak attack
• Press C to get into crouch mode
• Hold shift and press W to get behind a zombie
• Release Shift as you get near
• From the crouched position as you approach (still holding W) Hold RMB and then tap LMB to perform the sneak kill.

Sometimes you will stand and perform the action, sometimes you will just stand, but your arms won't raise.
It's like the client recognised the action and partially done the requirements (stood up) but then forgot to do part 2, which was raise hands (or weapon to ADS) leaving you standing there looking lovingly into the zombies eyes as he turns around and gets all cuddly.

In T159299#2206669, @Spaggie wrote:

Can we please add

Kcmav123

TheRunningManZ

sanguine00

To this ticket?

Thanks

Water is too wet

Here is a video of how it looks in 1st person when the ADS bug happens.

What he's trying to do:
Tap right click
Crouch
Hold breath
Video of ADS bug

The issue is a lot more common on servers where the player has higher ping. For me playing a US server makes it a lot more common due to higher ping than a EU server that has less ping.

This from SeniMJ via Joito

https://twitter.com/joitoo69/status/1407631915058962432

https://clips.twitch.tv/ZealousThirstyPancakeBCouch-dBTiGQJaKD1b34-7

https://clips.twitch.tv/MoistSpoopyVanillaKippa-2t7CfTz5kLKcHVGU

Both PoVs

What a surprise that trying to replicate it now, it's not happening the same way. But close. Video from 1.13 EXP.
Seems to kick in when pulling the gun out.
https://youtu.be/xdNM755Nxrc

Here is some extra feedback

https://feedback.bistudio.com/T158903

Other player's see you as adsing while this bug happens and you can shoot, but on your screen nothing is happening but other will hear you shooting.

Another video of it happening
https://www.youtube.com/watch?v=EhygFOWwhsc

Here is a video showing the melee issue that MeDarn described above….

https://clips.twitch.tv/EvilSourWatermelonJKanStyle-WFGvRtGzR42VDfhF

Here is hopefully some additional context for the 'ADS' bug. Here is a video of my reproduction of at least one scenario which results in a bugged gun raise state (https://www.youtube.com/watch?v=sjiwg4x5V-8). One of the easiest replication methods for me is possible with a gun in hand.

1. Shift+W to start running
2. As you are running, Crouch+hold Right Mouse Button at the same time to enter a crouch and raise your gun
3. Continue to hold Right Mouse Button, if you experience the 'ADS' bug, your client side will not have a gun raised, but your player movement will be slow as if your gun were raised.

Doing these combinations together seems to fairly regularly reproduce an 'ADS' bug. It seems as though on the client side, the right mouse button gun raise does not work, and your gun remains down. However, the server side seems to indicate that your gun is raised. You can see that in the player movement. The client side player tries to run/sprint like normal, but the server side keeps them at the proper speed as if their gun were raised. This created a stuttering movement for the player and helps indicate that they are currently experiencing an 'ADS' bug.

I reported this bug a while ago, seems to simply happen when you haven't ADS'd in a while.
https://streamable.com/6dfgnp
In this clip it takes nearly 2 seconds to ADS.

https://feedback.bistudio.com/T159436

Sorry to add more noise, but I think it's worth mentioning that we've been struggling with this bug to varying degrees for quite some time, and we think it can possibly be traced to changes made on 2/20/2020 related to a fix for "ghost bullets":

https://forums.dayz.com/topic/247626-stable-update-107/

This seems to be (at least in part), some of the relevant code changes:

https://github.com/Thurston00/DayZSAEnfScript/commit/a3e4550501566082722b109dc41e80f803a0e64a#diff-d637103b311ef7cb8f9129b18362205909279a73f61b21913efc94ecabdee9ab

Sorry if that sets anyone off on a wild goose chase, but based on our experience it seems a bit too coincidental when correlating the first experiences we were having with this bug with changes to DayZ's code. To the point where someone smarter than me might want to take a look. Thanks.

It seems to really be triggered now by those attempting a slow stealth CROUCHED approach to zombies looking for a stealth kill. When they arrive they right click to pull their weapon up and begin the melee process to find that their weapon is not lifting at all.

From here they are having to hit the button multiple times to get it to work missing their stealth kill opportunity. As of today we are getting a lot of reports of this exact scenario.

OOOh, nice point Sanguine, thanks for the data

Hello, I have multiple repros on video. Please have a look!

https://www.youtube.com/watch?v=hhtDHWIN0SA

Sometimes I can get it 95% of the time on our live server with my 40ms ping but the next day it'll only be 5% repro or less. We don't really have an explanation as to what could make the bug more or less frequent. I did try to add a small RTT latency (+5ms each way) using Clumsy (http://jagt.github.io/clumsy/) and it made the repro much more reliable while using it. Note that the last time I tried, using Clumsy on a local server didn't help reproducing the bug. But I haven't tried that again recently however.

In the video you can see the easiest way to reproduce the issue for me which is:

• Sprint while crouching (never release "W" or "Shift" during the steps)
• Tap "C" to uncrouch
• Then tap "Mouse 2" to ADS a few milliseconds later

If the repro is successful your character will sprint standing but will move at a crouch speed. I'm fairly sure that this is a desync where your character is prone and ADSing for game server but standing without ADSing on the client. A simple "Mouse 2" click will fix your local state (but no ADS will happen).

PS: I also show another issue in this video related to object in hands/inventory state where the game client has the wrong item in hands and can't unequip it.

I think the problem have its origin in the CHANGE OF STANCE.
For some reason, on certain servers more than others, switching from a stance to another (mostly from crouch to stand and vice versa) have some kind of glitch.
The character seems to have a sort of "bounce" in the process.

It can be noticed even on the little icon on the lower left side. This bounce is the origin of the ADS issue I think, because it's the origin of the character stuck in general in combination with other actions.
On the Official server I have a lot of difficulty to reproduce it, while on some private servers the issue is substantially constant.

On the Official I noticed that I can reproduce it more consistently if I spam change of stance during the exhaustion phase, when my character lose all the stamina and the regain start.
Here a video of the "bounce" in a private server. Look at the stance icon to have an idea what Im saying: https://www.youtube.com/watch?v=F454TBiH2wY

This is just getting worse by every patch it seems.
Now you can add a new problem that seem to be similar.

When you try to block your chr starts to block and then cancel the animation but in fact is still blocking if you keep holding s and right mouse bottom.
So just like ads issue you look to other's like your adsing but not on client side.

Been thinking about the ADS bug more with regards to the below code change from 1.07. It stands to reason that the "ghost bullet" issue that this code change intended to fix is essentially the "reverse" of the ADS bug:

• Client raises/ADS the gun
• Server desyncs and thinks the gun is still lowered
• Gun fires on client, but not on server

So they "fix" the ghost bullet condition with this code change, but inadvertently create the opposite condition:

• Server thinks gun raised/ADS
• Client gets stuck and doesn't complete the action, so the gun is lowered, client-side
• Player must go through the process of lowering and raising/ADS their gun to clear the condition (2x RMB)

I can't read code to save my life, otherwise I would try to pinpoint where this is happening and prove out this theory.

In T159299#2214438, @sanguine00 wrote:

Sorry to add more noise, but I think it's worth mentioning that we've been struggling with this bug to varying degrees for quite some time, and we think it can possibly be traced to changes made on 2/20/2020 related to a fix for "ghost bullets":

https://forums.dayz.com/topic/247626-stable-update-107/

This seems to be (at least in part), some of the relevant code changes:

https://github.com/Thurston00/DayZSAEnfScript/commit/a3e4550501566082722b109dc41e80f803a0e64a#diff-d637103b311ef7cb8f9129b18362205909279a73f61b21913efc94ecabdee9ab

Sorry if that sets anyone off on a wild goose chase, but based on our experience it seems a bit too coincidental when correlating the first experiences we were having with this bug with changes to DayZ's code. To the point where someone smarter than me might want to take a look. Thanks.

In T159299#2297057, @sanguine00 wrote:

Been thinking about the ADS bug more with regards to the below code change from 1.07. It stands to reason that the "ghost bullet" issue that this code change intended to fix is essentially the "reverse" of the ADS bug:

• Client raises/ADS the gun
• Server desyncs and thinks the gun is still lowered
• Gun fires on client, but not on server
  
  So they "fix" the ghost bullet condition with this code change, but inadvertently create the opposite condition:
• Server thinks gun raised/ADS
• Client gets stuck and doesn't complete the action, so the gun is lowered, client-side
• Player must go through the process of lowering and raising/ADS their gun to clear the condition (2x RMB)
  
  I can't read code to save my life, otherwise I would try to pinpoint where this is happening and prove out this theory.

I can confirm the issue with having to press RMB twice especially on very crowded servers, so I think you might be onto something

Thanks Geez, this is a biggie for some people if it's mitigated <3