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
I would like to suggest a couple new settings:
Client: boundaries, in % of screen. 0% means no freeaim; 100% means being able to move xhair to a side of the screen before moving point of view (default 0%)
Server: a)force freeaim (whether b value would be forced on clients or not, default off) b) forced freeaim value (default 0%).
So by default values clients would be able to use freeaim if they want to. Also they'd be able to fine-tune it. I doubt that those who use this feature would get a lot better, as it has its downsides too. Freeaim helps to stay aware of other targets while tracking down one. It makes recoil less headache inducing. On the other hand, it is harder to move around and doesn't help in CQB.
Also introducing % of screen as measurement value in Freeaim settings would solve (#217)[https://github.com//issues/217]
The text was updated successfully, but these errors were encountered:
that's not a bad idea. there should probably also be an option for the server to block client settings and force it's own, although it would be set to client side by default.
I would like to suggest a couple new settings:
Client: boundaries, in % of screen. 0% means no freeaim; 100% means being able to move xhair to a side of the screen before moving point of view (default 0%)
Server: a)force freeaim (whether b value would be forced on clients or not, default off) b) forced freeaim value (default 0%).
So by default values clients would be able to use freeaim if they want to. Also they'd be able to fine-tune it. I doubt that those who use this feature would get a lot better, as it has its downsides too. Freeaim helps to stay aware of other targets while tracking down one. It makes recoil less headache inducing. On the other hand, it is harder to move around and doesn't help in CQB.
Also introducing % of screen as measurement value in Freeaim settings would solve (#217)[https://github.com//issues/217]
The text was updated successfully, but these errors were encountered: