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
It's been reported that when someone scopes down a rifle, they can't change the direction of the scope view without leaving the scope and reentering it. This attaches a delay due to scoping up taking a moment (likely having a doafter line).
Potential fix: update scoped view on direction change?
The text was updated successfully, but these errors were encountered:
The problem with this is less so that they can't change direction of the scope, but the scope mechanic has a lot of janky things attached to it;
A very noticable lag/delay whenever the scope is scoped/unscope
A semi-often (especially with clients that is more lag-prone) chance for the scope to be "stuck", requiring putting the gun away and/or spamming the scope button again.
Certain guns that require ranging/adjustment being equally affected by the noticable lag/delay
A lack of documentation or knowledge of the scope hotkey--although this does not actually fix the noticable delay problem.
My suggestion is the following;
Keep the scope one-direction by default, allowing people to move while looking at the direction of fire.
Allow for direction hotkey change, my suggestion is ctrl + w/a/s/d to not only face the selected direction (in general, like how other places have that instead of requiring you to click to face a different direction) but also change the scoped viewpoint, allowing more QoL in using long-range scoped weapon especially in hallway areas like Greyson or Prepper.
It's been reported that when someone scopes down a rifle, they can't change the direction of the scope view without leaving the scope and reentering it. This attaches a delay due to scoping up taking a moment (likely having a doafter line).
Potential fix: update scoped view on direction change?
The text was updated successfully, but these errors were encountered: