In T145488#2647144, @Nate_LapT wrote:

I've been seeing this often since 1.25
is there a work around for this?
I've resorted to installing expansion and replacing bodies with graves.

If you hold RMB to ADS, check out my work around described here: https://feedback.bistudio.com/T179284

I've managed to recreate my pre-1.24 functionality - the ability to hold RMB and instantly ADS - by completely unbinding "Toggle Aiming Down Sights," then binding both "Eye Focus" and "Raise Modifier" to RMB.

I think DayZ devs need to re-work these "Raise Modifier", "Eye Focus" and "Toggle Aiming Down Sights" functions. Every modern FPS - especially those built on UE4/5 - offer players a switch to either "toggle ADS" or "hold button for ADS".

Yet, somehow, upon double-clicking RMB with the "Raise modifier" being the only function bound to it, ADS would activate for a split second and then aim would be dropped entirely

I've built up 30 years of FPS muscle memory and this patch killed it. :(

Still having this exact issue. Have abandoned the idea of using cfgweather.xml for now. Would be great if a fix could be prioritized. Weather is more important to my players than chain-mail, for example.

I have this exact issue and I also use NVIDIA Game Filters for sharpness.

@tarkules nice, neat work around. can anyone share a complete list of player classnames?

Video of bug here: https://www.youtube.com/watch?v=vgGSiei0QoU

Duplicate ticket for this issue here: http://feedback.arma3.com/view.php?id=22504

This has been a problem since the Alpha and really needs to be fixed.

Can confirm this issue no longer exists in version 1.48.131561.

Thanks!

This issue is still present in version 1.54 Stable.

I believe this has something to do with the aiming dead-zone.

I use pedals for helicopter control and setting the dead-zone to zero on the pedals fixed this issue.

Finding it hard to believe that no one else has noticed this...

This an ugly kludge designed to work around clipping issues; short-sightedness (again) on behalf of the devs.

For me, desync kicks in after the 3rd player joins the server. Everyone who joins after player #3 gets 100000 desync.