I think TheMasterofBlubb is referring to my comment in the other ticket:
Jul 6 2017
Mar 30 2017
Yesterday I upgraded my CPU from AMD FX-8350 to AMD Ryzen 7 1800X.
Besides the necessary change of the Mainboard and RAM (again 16 GB), everything else stayed unmodified.
I didn't even reinstall Windows, I just used exactly the same SSD and HDD (Arma is on the HDD).
Mar 28 2017
I just wanted to say, that I tested the hotfix RC today, but unfortunately there is no improvement for me... ;-(
Mar 17 2017
Hi aviatorboy1996, you are not alone! ;-)
Jan 10 2017
The same bugged zeroing behavior can also be observed with the TRG-20 and the (A)RCO optics.
You have to aim significantly lower than expected.
And it matches the same pattern with a largely deviating initSpeed between magazine and weapon:
May 10 2016
This is still bugged, even in the latest 1.56rc!
It would be nice if this could be fixed...
I found out that the mouse becomes less sensitive if you move it far left or right, and it becomes more sensitive if you move it less. So it seems like there is some mouse sensitivity adaptation enabled in the virtual reality map but not on Stratis and Altis?
Today I tried the newest 1.54 hotfix RC (1.54.133685), and this bug seems to be fixed. Thank you very much!
I think this ticket can be closed as soon as this fix goes to the stable branch.
I just tested 1.48 stable, and this bug is present there, too.
So this is not new to 1.50rc...
OK, todays version of 1.52rc (1.52.132483) has fixed issue 2 again. Thanks!
P.S.: None of your change logs seem to mention this fix. Did you fix this unintentionally? ;-)
Unfortunately, todays version of 1.52rc reintroduced issue 2. I hope this change will be reverted again for the 1.52 final.
I can confirm that issues 1. and 2. are fixed in 1.50rc. For issue 3., there exists an other ticket (as mentioned by Fighting Power). And the mentioned glitch is at least more complicated now:
Walking with lowered pistol against a wall and stopping there still makes the character to be slightly pulled into the wall, but simply pressing "s" afterwards is not sufficient anymore. You have to press "a" or "d" to walk sideways and use the mouse to rotate the body through the wall.
So I think the "correct" fix would be to _not_ make the character being pulled into the wall at all...
As the first three issues are fixed/duplicates, you might either close this ticket or keep it open to track the fixing of the glitch.
P.S.: Thank you very much for fixing the first two issues already! *thumbs up*
I don't know when this bug was fixed, but in 1.48 and 1.50rc it is working correctly. So I think this ticket can be closed.
Thank you very much!