You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a scope and pressing click to shot somewhere, if the shot there generates rotation for the player, the rotation happend before the shot is launched, which on itself removes you from the scope view, and up to that point nothing weird but, the thing is AFTER it removes you from the scoped view the player shot, and being the case than the view change, the positions in the screen selected by the mouse also change, which makes the shot going to OTHER POSITION DIFFERENT THAN THE ONE YOU INTENDED BEFORE, more often than not, the new position where the click should be provided you always had the non scoped vision.
What's the difference with what should have happened?
What should happend is than the shot should come before the rotation and camera change, this way you make certain than you shot where you intended even if you lost the camera afterwards, and of course avoiding with that any friendly fire or other accident generated by the shot after the camera change.
How do we reproduce this bug?
Equip a M41A
Get to the vendor of Scopes, select x4 or x2 and equip it in the M41A
Equip the M41A with the proper ammo type, any compatible rifle ammo type will do.
Go somewhere where you can have plenty of space to test the shot
Equip the M41A with both hands
Activate the scope looking to the north
Make a click to shot in a position to the north of you, but closer to the fathest WEST or farthest EAST from you
You will then notice the rotation and will see than the shot went somewhere else different than where you clicked before the rotation.
You can try this while looking at the EAST or WEST and pointing closer to the farthest NORTH or SOUTH too.
Attached logs
N/A
Additional details
Author: Obsdark
Admin: Cyberdie
Note: None
The text was updated successfully, but these errors were encountered:
Testmerges
#7909: 'Fixes maintainer access to the profiler and clears profiler access whenever admins are loaded.' by Watermelon914 at commit f10699e7c0
#7850: 'Acid Runner: Acid gen cap' by TheManWithNoHands at commit 67e1110f23
#7165: 'Fax Responders TestMerge Collection' by realforest2001 at commit 48de97d337
#8007: 'Frozen's Rat Competition Reward' by realforest2001 at commit 785b470ab7
#7607: 'Warden Praetorian rework (tm)' by Red-byte3D at commit 67a18edc72
#8034: 'reverts #6375' by cuberound at commit 482797ce9c
#8015: 'Mortar Changes' by Git-Nivrak at commit 3a6c587d2d
#7511: 'Weyland-Yutani Intranet Terminal' by realforest2001 at commit babe07fda1
#8049: 'Burn decal burn, hybrisa delaging' by cuberound at commit 846b67a03d
Round ID
25864
Description of the bug
When using a scope and pressing click to shot somewhere, if the shot there generates rotation for the player, the rotation happend before the shot is launched, which on itself removes you from the scope view, and up to that point nothing weird but, the thing is AFTER it removes you from the scoped view the player shot, and being the case than the view change, the positions in the screen selected by the mouse also change, which makes the shot going to OTHER POSITION DIFFERENT THAN THE ONE YOU INTENDED BEFORE, more often than not, the new position where the click should be provided you always had the non scoped vision.
What's the difference with what should have happened?
What should happend is than the shot should come before the rotation and camera change, this way you make certain than you shot where you intended even if you lost the camera afterwards, and of course avoiding with that any friendly fire or other accident generated by the shot after the camera change.
How do we reproduce this bug?
You will then notice the rotation and will see than the shot went somewhere else different than where you clicked before the rotation.
You can try this while looking at the EAST or WEST and pointing closer to the farthest NORTH or SOUTH too.
Attached logs
Additional details
The text was updated successfully, but these errors were encountered: