Those registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.I'm glad you found a solution that works for you though.
Quote from: VaeVictis on May 18, 2012, 06:43:32 PMQuote from: Elysium on May 18, 2012, 03:48:37 PMThose registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.I'm glad you found a solution that works for you though.i still seem to notice a difference :/Care to elaborate?
Quote from: Elysium on May 18, 2012, 03:48:37 PMThose registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.I'm glad you found a solution that works for you though.i still seem to notice a difference :/
Quote from: VaeVictis on May 20, 2012, 01:40:48 AMcan definitely notice when ever i dont have a registry fix in place... the built in client solutions just dont seem to cut it though it is possible its in my headmouse input in windows is a total bitch anyway, even different registry fixes will feel different Have you tried comparing your results with those registry fixes against m_directinput 1 (and 2) in either R1Q2 or Q2Pro? Keep in mind that AprQ2's DirectInput support doesn't seem to work properly. It's also normal to have to adjust your in-game sensitivity after the change.Those registry fixes are really meant as a last resort - it's almost always a better solution to take advantage of built-in support rather than trying to hack your way around it.It could also be that you're just accustomed to your current setup and any change to it feels wrong.
can definitely notice when ever i dont have a registry fix in place... the built in client solutions just dont seem to cut it though it is possible its in my headmouse input in windows is a total bitch anyway, even different registry fixes will feel different