Don't know if that's the reason, but when I've limited fps to 50, it was quite OK for play ... more or less, but definitely much better than before :D . Then tried to raise fps, but it was unplayable, so returned back to 50 8-)

In theory your fps (f) should ideally be related to max_packets (m) like this:
f=k∙m, k∊N

However, in reality UrT has loads of fps drops so fps drops cause this to be irrelevant unless you can keep your fps really stable.

And don't worry about not having your fps at 125, that bug has been fixed eons ago.

k∊N* actually =)
Better have 125 FPS if the refresh rate of your monitor is 60 Hz, because of flickering.
See post7694.html#p7694 (adv :)).

seta com_maxfps "30"
seta cl_maxpackets "30"

I meant on having exactly 125 and not one more or less because in the old times that was the only way to jump properly, but that's not the case now days.

As for page tearing, I noticed that only in one game: TORCS. I never use vsync, and I never (except for TORCS and a few more exotic examples like Ubuntu 10.10) saw page tearing in action, neither on CRTs nor on LCDs.

I frag relatively fine lately with this:

How do you define "relatively fine" ? :) 30 FPS is über crap for me...

And 30fps makes one frame last much longer than I have my reaction time, and it's not choppy to my eyes (I'm used to watching poorly encoded videos with 24fps and sometimes even lower).

Funny thing is, that my fully unoptimized config runs better then most who-knows-how-much optimized configs.

Except FPS in video games have nothing to do with FPS in movies...
30 FPS make one frame lasts much longer than your reaction time ? Maybe I didn't understand the sentence, but I really doubt your reaction time is below 33ms...

...