How do you clean this thing without destroying the material, keeping the grip etc? It has the typical "used" look now, imprints etc. Is not serious, but I like my pads clean.

Why I ping 20 ms higher than servers at the same location in QL? (15 ms CPMA, 35 QL, both servers UK).

Applies to all servers, there seems to be an overall +20 ms added.

Also, why the lagometer appears at that retarded position instead of being at the damn corner?

Can you add a simple custom laggometer in your hud like you do in CPMA?

Is anyone here able to play at the default rate of 125hz with the WMO 1.1a?

Shit is extremely sharpy. If you move your mouse in circles you notice it loads.

It still happens with 250hz, the only way to play without this annoying effect is by pumping it up to 500hz.

Now I keep hearing how overclocking a USB port to 500hz can damage the MB/mouse (specially because this mouse is really old). My MB is Gigabyte GA-X38-DQ6 so I guess there wouldn't be no problem when dealing with higher rates. I just want to be sure the mouse isn't going to stop responding because of being abused at 500hz, but i've always thought it was safe.

I don't get how people that has played in tournaments where hidusbf wasn't allowed managed to play at 125hz (afaik Stermy being one of those).

that blocked the weapons out of ammo. If you pressed the bind that switchs to a weapon out of ammo, nothing happened. Did they add this cvar that actually does something already? I see nothing but updates with irrelevant stuff, besides the lack of ztneage.

Tell me, so I can continue playing some 1v1 dm6.

pd: interested in any similar cvars that actually do something added lately.

First, I still dont get the in_mouse thing.

I use wmo1.1a with Microsoft drivers installed with hidusbf at 500hz.

in_mouse -1 (windows): If I select this, the speed of the mouse is afected by the speed of the mouse you select on the drivers setup, besides the sensitivity cvars.

in_mouse 1 (Directinput): If I select this, the speed of the mouse only is afected by the sensitivity cvars regardless the speed the cursor is set in the drivers.

I dont see any noticeable differences of feeling (yes, i do in_restart etc).

The weird thing is, if i remember well, in some versions this never was like this, or maybe it was in Q3 and not QL, i dont know and cba to install Q3 again.

Then about mousefixes, what I have is a file downloaded from ESR named "64304-mousefixes.zip" which contains a series of .reg files for different hz of your screen, then cplmousefix.reg, flatline.reg, and defaultwindows.reg

I would like to know wtf is up with that, whats the difference/advantages in going so anal about it by selecting a reg depending on your hz monitor rate and just not using the classic cplmousefix.reg aka mouse_fix.reg that everyone has used since stoneage for getting rid of the windows accel, if this applies to LCD monitors too, and also what flatline.reg is.

Finally, what I want to achieve with all of this is having a setup that is 100% guaranteed to translate on any computer so can I safely have the exact same mouse feeling when the proper reg file, hidusbf, and cfg business is installed on it. I just can't hit shit if im not feeling the mouse as it does on my computer.

PD: Another thing i just thought about, afaik if you go for example from 800x600 (from a CRT) to 1680x1050 (LCD), sens is not going to be the same. To people that goes to LAN: how do you solve this?

Because the rest of the maps suck ass.

Admit it and bring ztn back.

The cvar to stop the crosshair pulsing when you pick an item.

Just asking if this cvar has been added and I just don't know about it (its differently named now).

Also want to know if there is a way to move the lagometer to the corner of the screen, as it appears now a bit in the middle of the screen and its distracting. Or just a cvar that displays accuarte ms (someone mentioned it).

for playing Q3 and QL. Seriously. I love my CRT but I just don't have as much space anymore. What is the best in the market for not getting my eyes raped when I flick rails and shit.

Like playing and randomly getting the game stuck in a loop (game is freezed and sound loops), and the only way to get it back is by randomly pressing the console button or just smashing keys/mouse like a retard until it gets fixed, or maybe it doesn't and you have to restart oldschool.

This has been reported several times in the QL forum since forever but is still happening. Seems like a mouse related problem (1.1a here). They say its because of the polling rate, so you have to underclock your mouse because QL can't cope with that. Ridiculous since I don't have any problems playing Q3 or any other game @500hz, and QL is supossed to be a modern Q3.

There is a DI_BUFFEROVERFLOW error mesage going around randomly, it dissapears with in_mouse -1 but freezes still happen.

Going to try playing at the annoying rate of 125hz for a while to get another freeze and prove this is not even a mouse problem to begin with (posting this here since the same thing has been posted in the QL forums endless times without any success of debugging the issue).

For users with 3.0 and 1.1a (same sensor), its a must, since you can notice a huge difference between the default 125hz and 500hz. Some people say they have been finally accepted in LAN events, and some don't.

Can someone that actually attended events like ESWC clarify this?

If so, what top players use it? (using 1.1a or 3.0)

First is a mouse question.

I use wmo1.1a with the mousefix registry file for 0 XP accel. I also use the IntelliPoint drivers, because when going to LAN, when you have to play in some PC that isn't yours, people has installed already a hundred different drivers, making your sens a total mess. After uninstalling all the other drivers, I get the IntelliPoint installed and set mouse speed fadder to the same I use here, so I get the exact same sens.

Now, QL was ignoring the speed control of the IntelliPoint, even if set to max (the cursor going nuts fast on Windows) the sensitivity was the same in QL. I changed in_mouse from 1 to -1 and now the sens was being affected by the speed selected in the drivers, which is what I wanted. The weird thing is, a month ago or so, if I don't remember it wrong, I had to do the same thing inverted: in_mouse 1 was afected by the speed selected on the drivers, and -1 wasn't. Can anyone explain me what the fuck? Plus, I also see a lot of new weird ass mouse cvars.

I just tried in Q3 now, and both 1 and -1 are being affected by IntelliMouse's selected speed. Don't remember if always has been the same. Btw yeah, im doing in_restart after changes.

I just want a way to be able to get always the SAME sens everywhere by following the same steps of configuration.

The second question is, why the game still has ugly shadows when r_vertexlighthing 1, r_picmip 5, r_mapoverbright 5 etc? (qw style shadows).

Before formating my hd, I used to have Intellimouse latest version installed, with the "enable mouse precision" thing unmarked. The slider that controls mouse speed was irrelevant on Q3, which was nice, since that allowed me to have the same sens and accel (only sensivility and cl_mouseaccel controls it, as it should) regardless how fast your cursor goes in Windows.

After reinstalling XP and installing Q3, the slider is controlling the mouse speed of Q3 also, which leads to a fucked up, weird feeling.

I've already applied the Win XP registry file to delete XP accel, but theres no way to get my standard sens back.

The mouse is wmo 1.1a, and always used in_input "1".

I want to know what monitors are worth the money nowadays. I think its definitely time to move on from my huge 20'' CRT monitor (that is starting to die) and buy some LCD. I see a lot of people here talking about the bw226, but since there is the lottery of cheap panels going on, Im not sure if its worth the risk. Also someone mentioned that the "new bw226" (I don't remember the model) doesn't suffer anymore from cheap panels lottery, but I've readed on several forums that its still happening.

Basically, LCD's 20'' max for the best Q3 performance.

inb4 CRT.