Now while this is not exactly accurate on how a server talks to your computer it illustrates the lag in packet pairing responses. so he had a modified script that converted your computer from responding in pairs to responding to each and every individual packet/ping from a game server. The cycle would continue like that more or less through out your game sessions. Server : why didn't you answer me the first time? So when a game server sent you a packet it looked like this conversation.
PINGPLOTTER MANUAL FULL
It stated ( it may have been full of crap) that your computer sent and returned packets in pairs instead of 1-1. there was a script going around that modifed your network in an effort to reduce lag.
Now as to the wild a**ed guess on why this works for me.Ī long time ago i used to play wow on a different computer.
PINGPLOTTER MANUAL SERIES
select cmd prompt window press control C to end the ping series it will summarize how many packets were sent how many weren't, your minimum ping ( in ms) avg ping, and maximum ping. close eve after a hardcore night of screwing over your fellow man out of his iskies with internet spaceshipsĨ. Running eve on a K-pro you should be fine.ħ. it takes almost no cpu to run this so unless your while this is running in the back ground. The -t at the end makes it do it until you tell it to stop with ctrl-cĥ. The address tells it where to send these packetss. type with no alterations and minus the brackets (ping 87.237.38.200 -t) remember no brackets and space only where if you have completed steps 1 and 2 you should have a small black background window with simplified programmer UIĤ. for task manager go to file drop box and click run. in the search program or files box type cmd and hit enterĢb.
PINGPLOTTER MANUAL WINDOWS 7
INSTRUCTIONS IN WINDOWS 7 TERMINOLOGY ( CONVERT TO YOUR OWN OPERATING SYSTEM AS NEEDED)Ģa. having turned the cmd program back on every time i play eve socket closures are gone. Not un-coincidentally the socket closure made its return. To prove this i ran eve one day and forgot to run the cmd ping program on TQ's server IP address. Not running i managed to luckily(lucky timing wise not application wise) restart it when the error was occurring. when i earlier caught it with this program the cmd program was I haven't had socket closures while this cmd was running. So i have run this cmd program ever since when ever i played EVE and something interesting has happened. but rated the info with minimal packet loss despite the destination unreachable chunks. It told me destination net ( the IP address) was un-reachable for several seconds then told me time out and started to record ( this is in my bug report on the matter) So i restarted the cmd and i it turned on right in the middle of the event of the socket closures cause.
( this all the while i had eve in the background running) So after pressing ctrl-c to end the continuous pings it summarized the information i showed it to him and then i restarted it when i was making a bug report with info from screenshots and such ping command caught it as i was in the middle of cycling it to show my father how the cmd (ping -t)prompt was recording things. I have since found a workaround for it though.
0 kommentar(er)
