i recently aquired a mx518 logi mouse and im wondering whats best setup for it?? kinda like:

- use or not use logitech drivers (mouseware) and which version to use?
- any command line argument in ezquake (besides -dinput -m_smooth and -mwhook)

im using the following setup

- usb 1000hz patch
- registry mousecurve fix applied
- windows sensitivity set on 7 (from left to right, the bar got 11 dots.. im on the seventh)
- ezquake sensitivity on 3 without mouseware

any remarks, hints or improves.. plz.. im all ears =) (or eyes !!! =D)

500hz(usbmrs11) and NO drivers for the mouse, shitty stuff just ruined my sens everytime I started quake
fuhquake sens 7 and 7 in windows
no -dinput or whatnot

i'm using the setpoint drivers (english ones), swedish drivers was bugged for me

Windows:
1600 dpi set in the driver preferences
sensitivity in setpoint: 4th bar
pointer acceleration: none
500Hz patch

Quake:
cmdline: -noforcemparms -noforcemaccel -dinput -m_smooth
cfg:
m_rate 500
sensitivity 1.6

all buttons and the mwheel works and aiming feels good ingame, very satisfied with my mx518 \o\

feedback on peppe setup: pretty good precision but hard to find a good sensitivity to play with.. it seems like directinput can control sensitivity a lot better...

its a shame we cant use m_rate on ezquake =[[

imo the best settings are:
no mouse acceleration (der)
1000hz
cmdline: -noforcemspd -noforcemparms (dont bother with -dinput)
no drivers, two notches up from default (middle)
sens will prolly end up about 3.5 - 4.0 in quake.. although if you are used to a different style of play you may end up disregarding these comments entirely

also, it has to be said that 1000hz feels slower than 500hz, at least on takeoff.. i found this beneficial for shaft aim with these settings.. adding -noforcemaccel will slow my sens further, so i could use this with 500hz.. i just prefer the feel of this setup.

I'm running mine at 500hz (patch) with latest SetPoint drivers installed, using no accel and default sens.

As for ezquake I'm using -dinput -m_smooth in the cmd line aswell as m_rate 500 and sensitivity 4.

I'm running mine MX510 with 500hz, latest mouseware drivers sensitivity 5 in windows and 1 in quake (adjust it with m_pitch/m_yaw) no weird stuff in the cmd line.

hmm.. interesting... finally getting some conclusions with sens.. got one good setup using

1000hz patch
windows sens at 7
cmdline -dinput -m_smooth
m_rate 500
m_filter 0 (finnaly got rid of it.. at least for now =])
no setpoint or mouseware or drivers or anything else =D
maximum dpi using the dpi buttons on the mouse itself (pretty good stuff this buttons !! =D)


i get an accurate sensitivity 3 on ez... just more playtesting with this setup to make some fine tunning

seanos: i got pratically the same results u had here, but somehow the mouse felt weird with -noforceparms -noforcespeed... got 4.5 on ez using this but the mouse felt really weird... kinda like lagging or something like it

hrm.. wierd :/
i get no lag whatsoever.. ah well, glad to head youve found some settings u can use =]

You should ONLY USE -noforcemspd -noforcemparms when you find problems with the mouse, if you don't then don't use it.

if you don't use Windows for much else other than Quakeworld, Movies, Music, Internet+IRC then you are probably better off just installing a Linux distro. No mouse problems there.

i really have no idea what any of these commands actually do.. :p but ive discovered -dinput to be the fucking shit. been playing without it for so long.. silly me!

atm im using a couple of notches down from the middle bar... seems to be the best setting for it...

question: does -m_smooth add latency to the mouse? even a little bit? m_filter adds *alot*, relatively speaking.

ok, did a little testing then.. and imo it does add a *little* latency. its hardly noticable, though some quick reaction shots might suffer. it does seem to track slightly smoother, even with 1000hz. im keeping it off, it tracks smooth enough with 1600dpi ffs.

when using -m_smooth you should set the variable m_rate to your mouserate

ps.: m_rate is only avaliable when using -m_smooth

I use these settings with MX518 and its so smooth its unreal.

Setpoint:

1600dpi
disable game detection
speed/acc: OS implementation
pointer speed: 4th line
no acceleration

500hz patch

ezquake-gl

cmdline

+set vid_displayfrequency 100 // monitor refresh rate
-dinput
+set cl_independentPhysics 1 // so you can crank up fps

vars

cl_maxfps 231 // smoother than 154
cl_nolerp 0 // heaps smoother than 1
m_filter 0
sensitivity 2.25 // 11cm for 360 turn

Mouse pad is Everglide Titan clothpad. This is an awesome pad and is probably half the reason why this setup feels so smooth. BE

My aim is still shit but at least the setup is pretty much perfect for me ;-)

Hope this helps

im running mine MX510 (800dpi max) at:

500Hz @ xp pro (def's patch?)
4th bar in MouseWare 9.80 (en. version)
NO acceleration
ezquake.exe with -noforcemaccel ONLY, no -dinput
sens in qw: 10.5

800x600@150Hz, maxfps = 0

looks pretty stable and solid for me.