Mouse sensitivity slider what does it do for you?

[Greg 0]

The reason I havn't played OFP for almost a year now is simply that I hate the mouse sensitivity. Move my mouse a tiny bit and the cursor jumps several pixels making aiming a painful affair.

In any other game, the problem is simply solved by adjusting the mouse sensitivity slider, but not OFP. In OFP, dragging the slider to the far left (lowest sensitivity) acts like a 'dead zone' so moving the mouse slowly doesn't move the cursor at all, speed up, and the mouse jumps several pixels. There is no good explaination for this and no other game exhibits this problem. I can enable mouse speed adjustment in the driver, but that effects all games.

If I were to guess what the problem is, I would think the program does not store and accumulate fractional moves of less than one pixel, so any small movement on low sensitivity merely truncates to zero.

You're probably thinking I have a dodgy mouse, but this logitech mouse is fine, and I have two identical ones to compare. It is just plain fast and needs some slowing to make OFP usable.

Go on, move that mouse slider to the far left and tell me what it does for you? You may like to compare that effect to a the slider in say Unreal Tournament.

[Placebo 12]

Searching for "mouse AND logitech" finds a bunch of similar threads, including your thread from Feb/March last year, the solutions that did or didn't work then will be the same ones that will or won't work now.

[Greg 0]

Yep, that's the deal, none of those solutions help, and I did a new search incase a new idea turned up.  For a while I used a 3rd party program that enabled mouse speed change in games just before OFP started then disabled it afterward, but it never worked properly.  I realize it is way too late to get this (possible) bug fixed unless BIS decides to release source code of such to the community.

Edit: You can tell from the date on my last related post when I last played the game.  So frustrating for such a seemingly small issue. Although that post ended with 'problem solved' I only thought that because the new driver significantly improved the issue, didn't elliminate it.