in_mouse
hey, I've been experimenting the different values for in_mouse...
So from what i've read, :
in_mouse 1 is the classical q3 "mouse feel"
in_mouse -1 is the 1.17 q3 "mouse feel"
From what I've experienced,
in_mouse 1 is slightly sluggish, especially if combined with m_filter 1,
in_mouse -1 is very responsive.
I don't know wether one is more accurate than the other?
I've also tried with higher values and though 2,3 and 4 don't seem different from 1, do you notice the same?
lso, do you know wether in_mouse 1 or in_mouse -1 are different in any other terms than just plain "feel" (is one more precise than the other one, does one react better to fps drop than the other,...).
http://www.razersupport.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1&nav=0
u could try googling. or even searching the forums u know. cos this has already been mentioned.
-1 turns off buffer which can make a lags if you have mouse with overclocked usb etc i think
we buy G5 week ago, and at 500 or 1000hz mouse was stuck very owfen like autofire also fire was not clicked too sometimes,
so in_mouse -1 repaired that, also some buttons didn't work't so i bind them with some keyboard keys, and q3 detect them.
ye i have same problem with autofire without press button-mouse MX1000 I try reinstal drivers but nothing happen =(
its not logitech bug but sth in q3 engine. I and drill had prob with hold buttons on 1000 hz with g5 in q3 but in cs it works perfect.
btw. some can explain me what -------> in_logitechbug "0"
do ? is it helpfull to set it to another value ?

btw. some can explain me what -------> in_logitechbug "0"
do ? is it helpfull to set it to another value ?
its very old command from times when q3 engine has prob with mouse wheel in logi.
ok, then i change nothing here. Thank you Flex.
I have googled it I was just wondering what the E+ players thought about it.