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'm using version 0.99.402.
This happens in fullscreen only.
When running the game in non-widescreen mode (in my case 4/3 on a 2560x1440 monitor), the game cursor is slower than the desktop's cursor. I believe the total amount of "movement" needed to go from the left of the game's window to the right of the window is the same than the entire desktop's width.
In my case, the game's viewport (I mean, excluding the black bars) is 4/3*1440 = 1920px. But what's happening is that I need to move my mouse the same amount that I would need to go from the left end to the right end of my desktop (which is 2560px instead of the game's 1920px). This results in a "slower cursor" feeling. Nothing that makes the game unplayable, obviously, but it can be surprising.
The text was updated successfully, but these errors were encountered:
I haven't yet looked at the source code, so I don't know if this is possible, but you could in theory use the desktop's height instead of its width for your mouse sensitivity calculations (since the height stays the same whether you're in widescreen mode or not).
I'm using version 0.99.402.
This happens in fullscreen only.
When running the game in non-widescreen mode (in my case 4/3 on a 2560x1440 monitor), the game cursor is slower than the desktop's cursor. I believe the total amount of "movement" needed to go from the left of the game's window to the right of the window is the same than the entire desktop's width.
In my case, the game's viewport (I mean, excluding the black bars) is 4/3*1440 = 1920px. But what's happening is that I need to move my mouse the same amount that I would need to go from the left end to the right end of my desktop (which is 2560px instead of the game's 1920px). This results in a "slower cursor" feeling. Nothing that makes the game unplayable, obviously, but it can be surprising.
The text was updated successfully, but these errors were encountered: