Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouserate/FPS dependant turnspread #313

Closed
ETLegacyTeam opened this issue Mar 5, 2020 · 1 comment
Closed

Mouserate/FPS dependant turnspread #313

ETLegacyTeam opened this issue Mar 5, 2020 · 1 comment
Assignees
Labels
🐞 Bug Something isn't working cat: client Category engine (client, renderer, sdl) P3: Normal Priority 3
Milestone

Comments

@ETLegacyTeam
Copy link
Member

Author: S3ti (S3ti)
Date: 2013-06-09
Redmine Issue: 313, https://dev.etlegacy.com/issues/313


If FPS are higher than mouse polling rate, turning spread reduces.
If you get twice the FPS than your mouse polling rate (e.g 250FPS/125Hz) you get 0 added spread by moving your mouse.
Overall turning spread seems to be somewhat FPS dependant.
Maybe it's fixable or made selectable through a server cvar?

http://dev.etlegacy.com/boards/3/topics/513

@ETLegacyTeam ETLegacyTeam added 🐞 Bug Something isn't working P3: Normal Priority 3 labels Mar 5, 2020
@ETLegacyTeam ETLegacyTeam added this to the Future milestone Mar 5, 2020
@rmarquis rmarquis added the cat: client Category engine (client, renderer, sdl) label Mar 11, 2020
@jackeri jackeri self-assigned this Mar 17, 2021
@jackeri jackeri modified the milestones: Future, 2.78 Mar 17, 2021
@rmarquis rmarquis modified the milestones: 2.78, 2.79 Sep 28, 2021
@jackeri jackeri modified the milestones: 2.79, 2.80 Dec 23, 2021
@Aranud Aranud modified the milestones: 2.80, Future Apr 11, 2022
cakeET added a commit to cakeET/etlegacy that referenced this issue May 19, 2022
Removes the cap on spread growth for rapid mouse movements and with the +left and +right commands.

This resolves issue etlegacy#313 with FPS and mouse Hz and also stops an exploit where there is no spread growth when using a 180 turn script. Absolute maximum spread (255) is unchanged.

A side effect of this change is there is no longer an engine related advantage to making very fast mouse movements. Before this change, to control spread growth when playing, it was best to either move the mouse slowly or very quickly (to minimize the number of frames that the maximum amount of spread growth would be applied). There is still a general strategic benefit to moving quickly: the sooner you stop moving, the sooner your spread will settle.
Aciz pushed a commit that referenced this issue May 19, 2022
Removes the cap on spread growth for rapid mouse movements and with the +left and +right commands.

This resolves issue #313 with FPS and mouse Hz and also stops an exploit where there is no spread growth when using a 180 turn script. Absolute maximum spread (255) is unchanged.

A side effect of this change is there is no longer an engine related advantage to making very fast mouse movements. Before this change, to control spread growth when playing, it was best to either move the mouse slowly or very quickly (to minimize the number of frames that the maximum amount of spread growth would be applied). There is still a general strategic benefit to moving quickly: the sooner you stop moving, the sooner your spread will settle.
@Aciz
Copy link
Member

Aciz commented May 19, 2022

Fixed in 5d3226a

@Aciz Aciz closed this as completed May 19, 2022
cakeET added a commit to cakeET/etlegacy that referenced this issue May 19, 2022
rafal1137 pushed a commit that referenced this issue Sep 13, 2022
Removes the cap on spread growth for rapid mouse movements and with the +left and +right commands.

This resolves issue #313 with FPS and mouse Hz and also stops an exploit where there is no spread growth when using a 180 turn script. Absolute maximum spread (255) is unchanged.

A side effect of this change is there is no longer an engine related advantage to making very fast mouse movements. Before this change, to control spread growth when playing, it was best to either move the mouse slowly or very quickly (to minimize the number of frames that the maximum amount of spread growth would be applied). There is still a general strategic benefit to moving quickly: the sooner you stop moving, the sooner your spread will settle.
@Aranud Aranud modified the milestones: Future, 2.81.0 Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Bug Something isn't working cat: client Category engine (client, renderer, sdl) P3: Normal Priority 3
Projects
None yet
Development

No branches or pull requests

5 participants