It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
When looking around with a mouse while controlling the tank, the game doesn't register any input from the mouse unless you use fast motions to move it around. This makes aiming, especially precision aiming, basically impossible. Does anyone know how to fix this?
This question / problem has been solved by Lord_Kaneimage
avatar
Paul31286: When looking around with a mouse while controlling the tank, the game doesn't register any input from the mouse unless you use fast motions to move it around. This makes aiming, especially precision aiming, basically impossible. Does anyone know how to fix this?
I have noticed this myself, but so far my experiments have just involved messing with the mouse sensitivity and mouse acceleration settings in the options menu, I havent tried other methods yet.
avatar
Paul31286: When looking around with a mouse while controlling the tank, the game doesn't register any input from the mouse unless you use fast motions to move it around. This makes aiming, especially precision aiming, basically impossible. Does anyone know how to fix this?
avatar
Lord_Kane: I have noticed this myself, but so far my experiments have just involved messing with the mouse sensitivity and mouse acceleration settings in the options menu, I havent tried other methods yet.
I tried playing around with the in-game settings as well, but unfortunately, they don't really help. I also took a look at the nGlide config file in the game folder, but it doesn't have any control-related config options.

The weird thing is that the mouse works fine in other parts of the game. If you're in the main menu, or even the in-game map, there's no deadzone in the mouse movement. It's only an issue while you're controlling the wraith (or a citadel).
avatar
Lord_Kane: I have noticed this myself, but so far my experiments have just involved messing with the mouse sensitivity and mouse acceleration settings in the options menu, I havent tried other methods yet.
avatar
Paul31286: I tried playing around with the in-game settings as well, but unfortunately, they don't really help. I also took a look at the nGlide config file in the game folder, but it doesn't have any control-related config options.

The weird thing is that the mouse works fine in other parts of the game. If you're in the main menu, or even the in-game map, there's no deadzone in the mouse movement. It's only an issue while you're controlling the wraith (or a citadel).
I am probably going to take a look if there is some setting you can toggle with the mouse itself, some games like Dark Reign 2 for instance, have issues with mice whose polling rate is too high, time will tell sadly.
avatar
Paul31286: I tried playing around with the in-game settings as well, but unfortunately, they don't really help. I also took a look at the nGlide config file in the game folder, but it doesn't have any control-related config options.

The weird thing is that the mouse works fine in other parts of the game. If you're in the main menu, or even the in-game map, there's no deadzone in the mouse movement. It's only an issue while you're controlling the wraith (or a citadel).
avatar
Lord_Kane: I am probably going to take a look if there is some setting you can toggle with the mouse itself, some games like Dark Reign 2 for instance, have issues with mice whose polling rate is too high, time will tell sadly.
Oh, nice, your hunch was correct. Lowering the polling rate reduces the deadzone. The lowest value for me is 125 (default was 500), and while it's still not perfect, it's much better. I wonder if I could lower the polling rate even more somehow.
I am dumb
avatar
Lord_Kane: I am probably going to take a look if there is some setting you can toggle with the mouse itself, some games like Dark Reign 2 for instance, have issues with mice whose polling rate is too high, time will tell sadly.
avatar
Paul31286: Oh, nice, your hunch was correct. Lowering the polling rate reduces the deadzone. The lowest value for me is 125 (default was 500), and while it's still not perfect, it's much better. I wonder if I could lower the polling rate even more somehow.
Yeah I have a Logitech G502 and thats the lowest I can go as well.
Post edited May 14, 2016 by Lord_Kane
avatar
Lord_Kane: I am dumb
avatar
Paul31286: Oh, nice, your hunch was correct. Lowering the polling rate reduces the deadzone. The lowest value for me is 125 (default was 500), and while it's still not perfect, it's much better. I wonder if I could lower the polling rate even more somehow.
avatar
Lord_Kane: Yeah I have a Logitech G502 and thats the lowest I can go as well.
After googling for a while, it seems that 125 is the default polling rate for USB mice in Windows, and it doesn't seem possible to lower it even further. This is as good as it gets, apparently. Anyway, thanks for the help. :)
avatar
Lord_Kane: I am dumb

Yeah I have a Logitech G502 and thats the lowest I can go as well.
avatar
Paul31286: After googling for a while, it seems that 125 is the default polling rate for USB mice in Windows, and it doesn't seem possible to lower it even further. This is as good as it gets, apparently. Anyway, thanks for the help. :)
Turning up the mouse sensitivity in game while having it at 125 can help immensely too.
Thanks! Setting up a profile in Razer Synapse for Uprising 2 solves (almost) the issue. Normally my pooling rate is 1000, that was bad :) With Synapse it switches just for this game and reverts itself after. I guess other gaming apps probably have the same feature.

This should be stickied (tidied up maybe).
Raising the DPI rather then lowering it solved the issue for me. A DPI of around 8000 was able to overcome the deadzone while still being slow enough to be usable.
Post edited November 30, 2018 by hex357