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
Just remembered this game existed and glad to see it still exists!
I had trouble getting my mouse sensitivity to anywhere near a reasonable value using the in game options. I guess this could be related to hidpi modern mice and/or modern screen sizes/dpi's. Although easily fixed by finding the manual and editing neverballrc, it would be nice if the in game slider covered a wider range or allowed to input a value.
Aquick search in the code revealed in ball/st_conf.c:
If I am correct this suggest a max value of 100 + 50*10 = 600.
For me a value of about 1000 felt right (playing on linux with logitech mx anywhere 3 mouse at 1920x1200). I suspect a more correct way to get a value for range min/max would be to query the screen dpi and resolution and use that to come up with numbers that relate to the users particular hardware setup (just a thought and I may be entirely wrong about this!).
The text was updated successfully, but these errors were encountered:
Just remembered this game existed and glad to see it still exists!
I had trouble getting my mouse sensitivity to anywhere near a reasonable value using the in game options. I guess this could be related to hidpi modern mice and/or modern screen sizes/dpi's. Although easily fixed by finding the manual and editing neverballrc, it would be nice if the in game slider covered a wider range or allowed to input a value.
Aquick search in the code revealed in ball/st_conf.c:
#define MOUSE_RANGE_MIN 100
#define MOUSE_RANGE_INC 50
#define MOUSE_RANGE_MAX (MOUSE_RANGE_MIN + (MOUSE_RANGE_INC * 10))
If I am correct this suggest a max value of 100 + 50*10 = 600.
For me a value of about 1000 felt right (playing on linux with logitech mx anywhere 3 mouse at 1920x1200). I suspect a more correct way to get a value for range min/max would be to query the screen dpi and resolution and use that to come up with numbers that relate to the users particular hardware setup (just a thought and I may be entirely wrong about this!).
The text was updated successfully, but these errors were encountered: