have u checked for buiilt in accel and placebo

how does one check placebo?

as always, cg_placebo

much win.

How often does the temperature fluctuate in your room? Is your mousepad changing sizes?

That is not the problem I live in upper Michigan. The humidity doesn't change enough.

by how much?
something within 5% is fine if you apply different pressure and stuff like that

Around 30%. I usually can do 3 180 degree turns. When this happens I do 4 180 degree turns. I am thinking it could be bug with my mouse. I will have to do some more testing. I am using a steel series rival.

Use a ruler.

devmap [mapname]

Find some spot where you have a reasonably recognizable view. Type in viewpos. Pay attention to the last number.

Then holding the cord straight, move the mouse until your view is close to a 360 turn as you can get it. Type in viewpos to confirm that the last number is similar or the same.

As for the rival make sure its settings don't have any of the accel stuff on, that you are using in_mouse 2, and that cl_mouseaccel is 0.

Also what sens are you using at what DPI? Yaw and pitch are default right?

I am using 400 CPI and my sensitivity is 4.7. My mouse pad is a qck+ the mlg one. http://steelseries.com/products/surfaces/stee...lg-redblue Anyway I did confuse the amount of turns I do. I turn about 630 degrees with my sens after toggling the CPI back to 400 before I do about an extra 180. I don't have a ruler, but I do a have a tape measure somewhere. Or I could simply use my mouse pad to measure by changing my sensitivity.

O also I disabled the software to make sure the software wasn't buggy and this problem still happened.

All right here are the cm/360 for both. This is before toggling the CPI twice back to 400 CPI 38cm/360 and after 45cm/360. Just to clarify neither of these are the sensitivity that I play with.

Sens 4.7 at 400 cpi should be 22 cm/360

Are you sure m_yaw and m_pitch are 0.022?

Sorry I made no sens with that at all because I didn't really think you could help me from there and I just get confused sometimes.

These are the sensitivity's I used before 2.3
after 2.72 they both do a 360 on my mouse pad which is 45cm long so for some reason I need to toggle my cpi to 800cpi and back to 400cpi to get it to actually be 400cpi. Also the same thing happens if I use different cpi settings.

use the enotus mouse tool and get a ruler out...

try cleaning the sensor.

I've typed out multiple posts about the issue.

Unfortunately I can't look at my previous posts...

Here's a post on the ql forums.

http://www.quakelive.com/forum/showthread.php...tivity-Bug

you could probably search ESR forums on it as well.

apparently the newest firmware for the rival causes the dpi to fluctuate by 50 randomly
http://www.overclock.net/t/1432942/steelseries-rival/870

can try installing older drivers and reverting the mouse back to an older firmware: http://www.mediafire.com/download/38p3t7v50rq..._3.1.4.exe

Thank you. This has fixed my problem.

I used to have this problem with both my razer deathadder and abyssus and it drove me insane. =(

Finally solved it by backing up my config. Doing a cvar_restart and settings reset from the quakelive website.

Creating an autoexec.cfg with:
in_restart
exec dec.cfg


I used to have all my settings in autoexec, but that seemed to be my problem. Once I moved all settings to a different file and just execed that no more problems. Hope it helps.

So many problems like these yet nobody has a camera to record it actually happening.

Well I have something anecdotal, though I don't see how it's possible:

Logitech virtualized keyboard/mouse messes with mouse input. I recently discovered my G930 headphone dongle and plugged it back in. Mouse suffered all sort of accel/decel issues. Plugging the dongle back in had enabled the unnecessary Logitech Virtual Keyboard/Mouse devices/drivers for enabling the buttons I've never used on it.

As my mouse is a Zowie and driverless, and QL uses raw-input, the only thing I can imagine is that the G930 and other products featuring the same Logitech suite can reserve, claim priority to your usb ports, or simply overrun them with data. If your mouse is sharing a port with such a device, or dependent upon the robustness of the southbridge controller, your mouse will suffer in even raw input. Disabled the Logitech virtual devices and mouse returned to normal (headphones will still work as does volume scroll). I dunno if the buttons work, I suspect not, but I don't know that they are bound to anything or why I would press them in the first place :/.

I have the same problem. You have to stop changing sens and accel in the console every few games. It doesn't matter.

I already figured out what was wrong. It was a problem with my mouse. The newest firmware causes the mouses cpi to change. I installed older drivers and that installed the older firmware and the mouse is fine again.