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

Cannot set sensitivity other than int * 100 #168

Open
7HE-W0R1D opened this issue May 11, 2024 · 4 comments
Open

Cannot set sensitivity other than int * 100 #168

7HE-W0R1D opened this issue May 11, 2024 · 4 comments

Comments

@7HE-W0R1D
Copy link

I used to set the sensitivity of my Razer Viper V2 Pro to 650 DPI. However, this number seems not possible in RazerGenie. I cannot input numbers in the field, it seems to be only a indicator of the current sens. And the slider is only able to set sensitivities of integer * 100 (400, 500, 600, 700). I know 650 is possible because I set it once by editing some config under Linux.

Did I miss anything? Is this function available in RazerGenie?

Thanks in advance!

@z3ntu
Copy link
Owner

z3ntu commented May 11, 2024

Yes, I've recently also noticed this. When I initially made the UI I thought 100-DPI increments would be enough but I'm planning to reduce the increments to 50, so you can select e.g. 650 DPI.

Is this enough or do you also want some option to e.g. also select 653 DPI so in 1 DPI increments? The hardware does support this (or at least we can send it to the device), but I don't really think there's a use case for this.

@dodoradio
Copy link

could it be made so that you can set any integer dpi in the text box, while limiting to 50 dpi increments on the slider?

@z3ntu
Copy link
Owner

z3ntu commented Aug 28, 2024

Do you have a use case for that?

@7HE-W0R1D
Copy link
Author

Do you have a use case for that?

I've been having some busy time and didn't have a chance to follow, but a use case for @dodoradio suggestion would be:

For general users, the 50 increment will allow for quick adjustment to the sens they want (normally int * 100), they are also not sensitive to sens changes so 50 will be about right if they want to change and test a new sens, they are not looking for the accurate numbers.

For gamers / advanced users, they know what sensitivity they want and they know what the number means. So its okay to give them the largest degree of freedom to set the sensitivity.

These are just my initial thoughts :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants