has any of the settings u keep obsessing about ever helped you improve

I just get bored easily. But actually they have sometimes helped.

It affects the amount of outgoing packets which other players may or may not perceive on their end.

http://www.esreality.com/post/2548045/re-quak...pid2551129

Thanks that was helpful. I didn't think anyone would have any information about how com_maxfps effects packets.

affects?

how does it effect it if you use less than 250 but more than 125 for example 126?

read the linked thread closely, it does not make a difference if you use 125, 126 or 139. what you're asking about was common knowledge among q3 players, you probably could've searched/googled :p

my dick got 20cm longer since i use maxfps 180fps

do you measure from the base?

nope, just the bell

You measure from your anus to just beyond the tip.

Is all of this still valid?

http://www.mikemartin.co/gaming_guides/quake3_smoothness_guide

CL_MAXPACKETS

You can not use any MaxFPS value. The only valid values are those which are equal to (1000/x) where x is an integer. So for example your 125fps comes from (1000/8 = 125). If you try and set MaxFPS to 120, you will still get 125fps. This is because any invalid setting is rounded up to the next (1000/x).

Some valid Values for MaxFPS:
1000/3 = ~333
1000/4 = 250
1000/5 = 200
1000/6 = ~166
1000/7 = ~142
1000/8 = 125
1000/9 = ~111
1000/10 = 100
1000/11 = ~90
1000/12 = ~83
1000/13 = ~76
1000/14 = ~71
1000/15 = ~66
1000/16 = ~62
1000/17 = ~58
1000/18 = ~55
etc.

CL_MAXPACKETS AND COM_MAXFPS
This is where your graphical framerate affects your connection. The actual MaxPackets sent to the server MUST be equal to (your_FPS/x), once again where x is an integer. If you set your MaxPackets to a value which is not equal to (your_FPS/x) then your MaxPackets will actually be rounded down to the nearest valid setting.

Most of you will use MaxFPS 125. If so, your valid MaxPackets values will be as follows (assuming your PC can achieve its MaxFPS value constantly):
(always round up these calculations to integers)
125/1 = 125
125/2 = 63
125/3 = 42
125/4 = 32
125/5 = 25
etc.

You should choose the largest value that your connection can handle. If your MaxPackets is not set to a valid value, it is a potential waste of bandwidth and therefore potential lag/instability.
For example, if your framerate drops to 100 then your valid MaxPackets values will change to:
100/1 = 100
100/2 = 50
100/3 = 34
100/4 = 25
etc.

So if you have your Cl_MaxPackets set to 100 and are using 125fps then mostly your MaxPackets will be at 63 (this is the largest value not exceeding the input Cl_MaxPackets limit). However, when the framerate drops to 100fps, the MaxPackets will change to 100 as this is now the largest value that does not exceed the input Cl_MaxPackets limit.

The first part about the valid values for com_maxfps is still true. I don't know about the rest but if it was true once I guess it still is.

well........
let's say it's not but I can't be bothered to explain the details?
It's fairly close at some points though, but you should realize that everying in QL is done based on FPS. At each new frame QL looks at the time since last doing something.
If that exceeds some threshold then it decides to fix that and update the "last time it did that action".

So for instance with sending packets...
If your FPS are drawn every 6ms (166fps), while you have maxPackets on 125 (8ms).
Then QL will check if 6 >= 0+8 to decide if it should send a new packet.
since 6 < 8 it won't do that.
Next frame the time is 12. 12 >= 0+ 8 -> send a new packet, new time for "last send" = 12.
then next frame 18 >= 12+8 -> don't send.
next frame 24 >= 12+8 ye
30 >= 24+8 -> meh
36 >= 24+8 -> yeee

etc etc

changing fps changes your sound?

wtf

Do you even play this game?

:D

do i have the choice to even change my fps brah?

com_maxfps and then a number I think the ranges are 30 to 250.

i am well aware of that

Good to know.

lol