A crap load of tests over a period of time will give you a better understanding of how the network is actually behaving. If you run a single test, you run the risk of capturing data that does not represent the actual situation. Network performance varies naturally over time. In reality, forming a reliable diagnosis with a single traceroute does not happen. That must mean hop 3 or 4 is involved with the problem." With traceroute information, the goal is to inform a diagnosis that looks something like: "Response times look good until the third hop. Instead of only measuring response time for the game server, traceroute measures every router, or hop, between your computer and a target destination. It's great for letting you know if your network is fast or slow but doesn't tell you what's slowing it down. This measurement is commonly referred to as latency. Ping tells you the number of milliseconds it takes your computer to get a response from a server. Once you've found the right target, you're ready to start testing the network.Įvery computer has built-in tools for measuring network performance. A quick email to their support team can get you the information you need as well. Usually, the correct server address can be found on the game's website or forum. Sometimes lag only affects a game server, so it's important to make sure you're testing the right target. ) instead of the server that is actually hosting the game (e.g. When you're testing a game server connection, a common pitfall is testing the company website (e.g. The basic concept behind finding the culprit is testing the network and looking for places where performance breaks down between you and the game server. You can find the source of lag problems the same way technicians at the game companies do - by analyzing your network. A little upfront work can be time well spent. Your solution path depends on where the problem is located, and diagnosing the right problem before you begin saves time and frustration. In fact, network problems occur in three general places: It is possible to experience game lag not caused by the game server. It helps you fix the right problem, with the right people, instead of hitting dead ends with tech support. Fixing game lag is similar - better information gets you to the source of lag problems faster. It's just Mario had an objective, and knowing the right castle would have given him a shortcut. Nothing against the dudes in the other castles. If Mario knew which castle the princess was in, he could have gone straight to the prize instead of wasting time-saving a bunch of Toads. Testing the network for the source of the problem is the best way to figure out who the right people are, but beware, there is a chance you are the right people. The key is getting your problem in front of the right people. It sucks, but you can do more than flip your router on and off. If that's the case, you'll be lagging so hard your bullets won't hit anything until yesterday - nobody is gonna want to play with you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |