original is stronger than stock rocket launcher in mge.

stock rocket launcher is better for horizontal jumps, and you can abuse some corners with it.
original is better for vertical rj's (very slight) and is easier to aim because you don't have to compensate for right side (its simply and logically the truth)

now you won't see me crying about it in mge (that's just retarded), but I can kind of understand how it can be called a crutch. you need more finesse with the stock rocket launcher.

clearly tas demo

http://steamcommunity.com/groups/beball
should say "Group for retired NA TF2 bball players and old people"

jdawg is the last hope dude.
the evil doctor nostrand stole our talent like spacejam.

im referring to

your own rockets are displayed in the same manner as an enemy rocket, as in they spawn and are tracked on the server and the server relays where they are to you. the server also relays where the players are to you.

I don't see how the discrepancy he describes is possible. I mean they may not appear where they actually are, but neither does anything else cause lag. the rockets you see are in the true position, they are correct relative to enemy players.

the thing that is not correct here is where you appear to be, the rockets will feel weird because they are being shot from your true position while your player position appears lag compensated ahead by an amount relative to your latency+interp.

(and that with the delay is why soldier sucks at high ping/interp)

Valve has several mistakes in their documentation (which can be proven), but this isn't one of them.

I don't see how this can be, rockets are not client side.

ya that's what I meant. :)

it can be misleading for some people is what I mean, not that it's wrong^
because he was asking about cl_interp_ratio being limited to 1 in ESEA, which is a different from the ratio 2.2 you're talking about

k thats what I thought^^

1. (rate) because you can lag/get dos'd from the server. If it uses that much bandwidth something is wrong and you don't want to let it.

2/3. (sv settings) I only asked about the calculation because I was confused when you said it limits your lerp. your post couldn't be right unless my math was wrong. I know I can use 100 lerp, 67 updaterate, on default sv_client_max_interp_ratio (5), but the math says 14.9*5=74.5ms.

so sv_client_max_interp_ratio can't limit cl_interp/lerp is what I was getting to

rate 903468349634908 > 500000 amirite?

that's what makes it broscience. you can't assume the games framerate is in sync with the monitor hz because it won't be. no one uses vsync because its terrible.

I would imagine there's other issues but we don't even need to get into them to know it's a bad setting.

are you saying 2*66 = 132ms or 2*15.15 = 30.3ms?

for your cfg

rate 100000 is overkill already
rate "500000" = equivalent of fucking dead corpse

cl_smoothtime 0.01667 // 16.67ms (1/60sec, set to 1/[fps of monitor])
broscience (so is fps_max = monitor*2+1 btw.) (and who uses 60hz?), just use 0.01 if you're using cl_smooth 1.

sv_client_max_interp_ratio 2 = unecessary and pointless when they can just set a giant cl_interp number.

doesn't cl_interp_ratio merely multiply your cl_interp by that number
so you can get the same result by leaving ratio at 1 and setting your interp higher.

saying ratio 2.2 and interp 0.033 is misleading
the settings it means are cl_interp_ratio 1, cl_interp 0.033 (or cl_interp 0, cl_updaterate 66, cl_interp_ratio 2 which equals the same thing)

jitter buffer is the extra interp above 0.0303 which I would also recommend.
even on soldier I use cl_interp in the range of 0.016 to 0.02 for that reason.

if your teammate has 900 ping, its probably not ddos, more like a shitty connection. however since the internet still works in some capacity your friend can easily check if its ddos. (by typing netstat -a, router logs, wireshark etc and looking at the connections).

if some retard is trying to dos by pressing 2 buttons in loic or something we might even get his ip and be able to retaliate. the chance of the attacker being retarded is high, as evidenced by the internet still being up (if there is an attacker at all).

maybe ascertain that it is in fact ddos before posting random shit?

ctrl.
In the past I broke the ctrl key multiple times (jumper problems?) so I used shift a lot as well.

ya, its not really a fault with p-rec, just demo recording lag. not that uncommon

Yes.

No problems.

fk1