General DiscussionHelp me TECH SAVVY PEOPLE (Dota 2 is unplayable: high packet loss).

cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_interp "0.167" // Interpolate object positions starting this many seconds in past (Default 0.055, Min 0.033)
cl_interp_ratio "-1" // Multiplies final result of cl_interp (Default 2)
cl_smoothtime "0.01" // When errors occur smooth display over X time, 0 Disables (Default 0.1)
rate "80000" // Total amount of bandwidth Dota 2 may use (Default 80000)
cl_updaterate "101" // Amount of updates recieved from server per second (Default 30, Max 30)
cl_cmdrate "101" // Amount of updates sent to server per second
cl_pred_optimize "2"

I have it too on normal client, i just installed reborn, works good

@Sir: Thank you but I don't think that helped :(

Please help me everyone!

What country and isp?

I live in the Philippines and I use PLDT. I know that it's given me so much shit before, but I don't think this is a problem on the side of my ISP anymore.

That is the problem man. Is documented in dev2doto that PH ISPs routes your connection to various places in the world during peak hours resulting in request timed outs in SEA server.

The only alternative man is to play in USE and USW, albeit the high ping, but will give you stable connection all the time.

I have had routing issues with PLDT but it has never been this bad though.

(And according to cmd, the tracert i ran on SG servers did not route my ping elsewhere. It either went straight to sg or it went to viet/thai then SG)

This issue only occurred when I reformatted my computer and installed a fresh version of dota. I know I had some network settings in my old cfg file but I forgot what they were or where I got them from, which is why I think it could possibly be from that.

trust me man, it all boils down to the isp if there are packet loss.

its either your dsl cables are damaged or the isps routing during peak hours in your country is not good.

go to cmd and type this -> ping sgp-1.valve.net -t and this ping sgp-2.valve.net -t wait for 5-10 mins

if you see a lot of request timed outs, thats your packet loss man during peak hours, if you still have packet loss during off peak then your isp must really suck man, cant do anything bout that anymore, well on both cases you cant do anything really, you just have to find a server that got good routing such as USW and USE.

now try this ping eat.valve.net -t this is the usw server, your isps routing to this server should be good, albeit the high pings, should have no request timed outs.

But if I have this problem, doesn't this mean that my friends that have the same ISP as me should also have the same problem regarding packet loss?

Just ran the cmd command, and I had no request timed outs so far. (This has been true in my cmd tests the previous days which is why I think it could be my cfg settings but I'm not sure)

Also, if it is indeed my ISP, then I am screwed. They are notorious for not doing anything to fix these kinds of issues...

continue monitoring your cmd in both sea servers on different times. packet loss can be unpredictable.

Alright, thanks for taking your time to answer my questions.

Any idea on what I should do after? (Like if there's anything I can do on my end and not on the side of my ISP?)

you can remove other variables man like check if theres someone in your house downloading if youre on wifi, check for spyware that might be eating your bandwidth, stop downloading while playing etc.

also test some games during peak hours and non peak hours, this is very important. if there are no packetloss in SEA during OFF peak, like 5am or something, then its all on your ISP man.

Alright, thanks for the help man!

If anyone else has any other ideas to help me, it'd be welcome!

bump