[odamex-bug-reporter] [Bug 763] Odamex mouse upgrades.
- From: odamex-bugtracker@xxxxxxxxxx
- To: odamex-bug-reporter@xxxxxxxxxxxxx
- Date: Thu, 05 Jan 2012 20:26:46 +0000
http://odamex.net/bugs/show_bug.cgi?id=763
Dr. Sean <grandpachuck187@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grandpachuck187@xxxxxxxxx
--- Comment #1 from Dr. Sean <grandpachuck187@xxxxxxxxx> 2012-01-05 20:26:46
UTC ---
An update on the info Alex posted:
Other ZDoom derived ports use the in_mouse cvar to control the source of mouse
input, with 0 (default) using the preferred input type for the OS. On Windows
platforms, that means using the Windows User32 library (in_mouse 1). The other
choice on Windows is to use DirectInput (in_mouse 2), but few users select
anything besides the default.
Mouse input fetched by the User32 library is first subjected to mouse
acceleration and then scaled by mouse sensitivity setting the user selects in
the Windows Control Panel. Mouse input also is clipped by the current screen
resolution.
Mouse input fetched by DirectInput is not affected by Window's mouse
acceleration or sensitivity setting or by screen resolution. The input is raw
and relative to the previous mouse input event.
Odamex only uses only DirectInput for mouse input. In order to provide mouse
response faithful to the ZDoom defaults, r2694 will algorithmically mimic the
User32 mouse acceleration and sensitivity scaling based on the settings in the
user's Windows Control Panel.
--
Configure bugmail: http://odamex.net/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Other related posts:
