Hi,
I have a Logitech M500 7-button corded laser mouse and the ONLY way to use mouse wheel Tilt Left and Tilt Right (buttons 6 and 7) is to assign keypresses TO them via the Logitech SetPoint software. Both SetPoint (v6.67.83) and the Logitech mouse driver (v5.90.41) are up-to-date, being the LATEST versions available.
I've used SetPoint to assign Numpad7 to Tilt Left and Numpad9 to Tilt Right. These assignments work fine in Windows 10 (e.g. in Notepad with Num Lock switched on, Tilt Left types a 7 and Tilt Right types a 9. They also work fine in most games. However, in TWO of my games (far Cry Primal and The Witcher 3), they simply don't work at all.
In Far Cry Primal, I want to use Tilt Left for Beast Attack/Move and Tilt Right for Recall Beast. This fits with my control scheme, as I then don't have to move my other (keyboard) hand, but simply press the mouse Right button to aim, then the appropriate wheel Tilt button to control my beast companion. Very fast and efficient. But in the Options > Keyboard and Mouse > Customize Controls menu, any attempt to press Tilt Left or Tilt Right to rebind an action doesn't work (as if NOTHING has been pressed). Pressing Numpad7 or Numpad9 on the keyboard works fine, but not from the mouse Tilt buttons which are supposed to be issuing those keypresses.
Odd thing is, SetPoint used to work fine with Far Cry Primal AND The Witcher 3, but suddenly stopped working, presumably after one of the game patches. I suspect this is because, to resolve mouse lag issues, the developers have switched from high level Windows-based (slower) mouse support to their own internal low-level (faster) mouse support, which communicates with the mouse driver directly. Unfortunately, this approach bypasses any high-level software that reassigns mouse buttons to keypresses, rendering any gaming mice with reassignable buttons useless. Anyone with a Logitech G500 series gaming mouse would have the same problem with their Logitech Gaming Software, for example.
Has anyone had similar issues with mouse button rebinding in Far Cry Primal? If you've managed to solve it, please let me know your solution so that I can try it.
Many thanks in advance...
Yay! Found the solution, and an oddity (bug?) in SetPoint behaviour!
I'd wanted to use SetPoint to map the mouse Tilt Left button to the Numpad7 key and and Tilt Right to Numpad9. To avoid confusion with the 7 and 9 keys on the top row of the keyboard (which are typically used for weapon selection), I turned NumLock OFF so SetPoint showed them "correctly" mapped to Numpad7 and Numpad9 rather than 7 and 9.
But, on startup, my keyboard defaults back to NumLock ON and they work OK in Notepad (typing 7 and 9) but won't work at all in the affected games (behaving as if nothing is pressed).
So I remapped them in SetPoint with NumLock ON this time and they now read as 7 and 9, still type 7 and 9 in Notepad and, in the affected games, they now WORK but oddly enough read as Numpad7 and Numpad9!
Weird... But as long as my button mappings now work as intended again, I'm not complaining.
Looks like the problem lies with a possible bug in SetPoint. It shows numpad keys assigned correctly according to NumLock state, issues correct key scan codes when NumLock is in the same state as when assigned, but won't work correctly when NumLock is in the opposite state.
So, if anyone else has this issue when assigning mouse buttons in SetPoint to numeric keypad keys and they work in Windows but NOT in-game, assign them with Num Lock ON, not OFF! SetPoint will appear to show them incorrectly, e.g. 7 instead of Numpad7, but they'll will work fine in Windows AND will appear as numpad keys in-game.
Hope this helps...