afaik yes
also such changes have no practical effect on gameplay in my opinion

Tell that to Cooller, Cypher and Av3k

all of them were using 1 the last time i checked

Cooller is computer illiterate, cypher doesn't know wtf the command does ( he has actually used 0 for most of his q3/ql career iirc ) and av3k is polish.

i think i can agree with all of that. your point?

Well, cooller probably uses it because it was default back in q3 / someone else he looked up to used it and cypher has changed it several times ( the argument being that he didn't knew what it does when someone asked him ). So no, I doubt they consider it has any gameplay effect.

exactly

you should have never asked because if you know placebo won't work anymore..

Not necessarily. You can't be 100% sure it's placebo, so it can still work.

Most of the times it's a placebo that you have a placebo.

I use m_filter 27.3758; fits best for me.

Lets get serious..the thing is that if you use high mouse pooling you shouldn feel any diference until m_filter 5..I use 250hz pooling rate and i feel the difference at m_filter 2. I think this command comes in handy if u use 125hz or 250hz mouse without hidusb or other things that increase usb port pooling rate..(not an expert just personal experience. I used mx518 at that pooling and with m_filter 1 and it was better that without m_filter.)

It's a boolean value (either 0 or 1) to enable mouse smoothing...

not in ql

I stand corrected.

Well, it's no wonder the tracking in that game is so horrid...

q4 always felt weird as fuck to me even with m_filter set to 1 ( which is the smallest possible value iirc as the engine defaults 0 to 1 ).

Did I miss some voodoo tricks?

in q4 the setting was 1-10 I think, 1 = off, dunno why it was like that.

Well 0 is still off, but its not a boolean, since you can set it from 1-33 when its on.
I don't know about settings like 0.5
I think you can confirm it by typing in m_filter in the console and pressing enter, it tells you the range of options.

i can feel the diff on filter 1 and 0, filter 0 stops too slow, filter 1 takes an extra .005 sec or something of movement when i move my mouse.

for accel, m_filter 1 is nice, lets you glide more *, for no accel use m_filter 0, more precise

*unless u have a rough textured mousepad, then its shit

.005 sec OMG you, sir are a wunderkind.

i am ze uber

didnt anyone explain m_filter 1 takes two input buffers and takes the average of them?
so on m_filter 2 you get 4 input buffers or what.
and on 0.5 you get the average of the average. got some MANOVA in there or what....

The pure concept of m_filter is retarded. Why anyone would want to use this is beyond me.

if only quake had a funday monday with day9, so we would all have to put m_filter on 30 and see who wins, derp

*bump*

I am not satisfied with any of the answers here. I want something more definitive please. Is m_filter lower than 1 doing anything in Quake Live or not?

0 < m_filter < 1 <-- what does it do?