Have you tried this that was previously mentioned in this thread? The first part (adding the following commands) worked a charm for me.
It's not the mouse accel or vsync that's bothering me. I do have those things in the ini files.
It's the fact that the X and Y axis have different sensitivies while in the menu. Here's what I've gathered:
- DEFAULT: In single monitor 16:9, the X axis is more sensitive than the Y by a proportional amount to the aspect (I'm guessing). Either way, the X is sensitive enough that it feels very awkward to do anything with the mouse in menus. The aim sensitivity is fine. Every menu can be navigated by arrow keys (even the pip boy using shift + arrows)... EXCEPT for the VAT menu (as far as I can tell). It's a 'working' solution, but it feels very clunky and I always like to use my mouse first. In 48:9, the mouse is practically unusable in menus due to the fact that the X-axis goes berserk (much like Metro2033).
- INI EDITS: There's two things I can change in the ini files to tweak the mouse with respect to this issue.
1) bBackground Mouse=1 (default is 0) will make the mouse have 1:1 sensitivity in menus. The mouse then becomes super sluggish in the menus though. I end up using my higher DPI setting on my G500 and turn down the aim sensitivity to compensate. This works perfectly EXCEPT when the mouse reaches the edge of the screen, it will sometimes minimize the game when I click (i.e. shoot). When I maximize the screen again, the mouse is back to its old self (the default).
2) fXenonVertLookSpeed = 1200.0000 and fXenonHorizLookSpeed 1500.0000 (default). If I change the horizontal look speed, it does nothing to the menus. All it does is change the aiming sensitivity as far as I can tell (in reality I actually didn't notice squat by changing these values EXCEPT when the xbox controller is plugged in. I.E. changing fXenonHorizLookSpeed to some absurdly low value doesn't make my mouse aim sensitivity change, but it does make my controller x-axis aim sensivity super low. I'm going to guess these values are actually for the look speed of the controller and not the mouse).
Right now, I'm trying out a DPI setting that sets the X-axis lower than the Y-axis and seeing how that works. I somehow made it so that the default menu sensitivity behaves like 16:9 instead of 48:9 (only 1.5x more sensitive in X as opposed to 9001x more sensitive).
I REALLY want to use Kb/m for three main reasons over my xbox360 controller (the controller is 100% functional for a CONSOLE experience): 1) console commands (kb is disabled when in 360 mode), 2) The third person mode where you rotate about your character is not smooth at all with the controller, not sure why, 3) QUICK SAVE (no such function on the controller).
EDIT: Just tried using 1600 DPI for Y and 800 DPI for X. The menus are now perfect. But... my X-aiming is super low now. Changing the XenonLookSpeed values don't affect my mouse at all. How in the world did this mouse sensitivity retardation get past QA? Or did they test the PC game using a xbox360 controller?
I'm now just going to live with the hyper sensitive X in the menus and hope I get used to it.