Hi everyone, We are working to compile relevant information together to better track possible network issues some users are reporting. If you are having issues such as double swing/casting or unstable ping/disconnects that you are only experiencing playing Darkfall: Rise of Agon and not on websites or in other games, please read on. We will need some data from you to track possible network issues that we can solve. You can go to the form here to see everything we'll need. Some important tips/steps: ***Note: Please ensure to turn off any downloads/uploads before doing ANY of the tests below as it will skew the results. This includes torrents and any computers connected to your internet in your home, not just the one you are testing on.*** Running a trace route Windows Open the Start menu Click on Run (If no run, look for a search box or usually you can just start typing) Type "cmd" and then press the OK button to open a command prompt window At the prompt window, type "tracert login.riseofagon.com" and press the Enter key To copy the output, right-click anywhere in the window and select Mark. You can press Enter to copy all of the output, or select the text you want to copy using the left mouse button and then right-click with your mouse. Paste the copied text into the submission form(see above for link) Example: Checking your connection speed This is done by going to a speed testing site to get an actual test of your upload and download speeds. www.speedtest.net is a commonly used one. Make sure that it finds a server close to you as the closer the test server more accurate the test will be. Put in the form(link above) what your upload and download speed results are, make sure to turn off any torrents or downloads/uploads on any computers connected to your internet to ensure the test is accurate. Running a ping test Windows Open the Start menu Click on Run(If no run, look for a search box or usually you can just start typing) Type "cmd" and then press the OK button to open a command prompt window. At the prompt window, type "ping login.riseofagon.com -n 100" and press the Enter key(This will take a few minutes!). The longer you run the ping the more accurate the test, replace the 100 with any number up to 1000 if you have the time and want to have a more thorough test. We just want the"Statistics" that come up at the end of the test to show the minimum, maximum, average response times and % of packet loss. To copy the output, right-click anywhere in the window and select Mark. You can press Enter to copy all of the output, or select the text you want to copy using the left mouse button and then right-click with your mouse. Paste the copied text into the submission form(see above for link to form) Thank you to everyone who helps us in this endeavor by completing the form located here. Sincerely, - The Team at Big Picture Games
Not that this information won't be helpful to you, but this is not a network issue. I get the ghost swings/casts constantly and 95% of the time it is with a steady 85-90 ping. I have run trace routes, pings, speed tests.....all normal. So unless you have a way for me to test the traffic between the actual client and the actual game server, I don't think you are going to find much.....that said, I will fill out your form.
i think its from brief server stalls, they should be able to check on their end. If its single core server or cluster of single core servers that talk to a master server they should be able to get a good idea on thread usage and pin it down that way. Im sure some people have routing issues as well, but wouldnt be surprised if some of our issues arent micro stalls.
They were normal when you ran them. They may not have been normal when you had the problem occur. Unless you had a traceroute running at the exact moment you had an issue (and I mean exact) and it was pinging the exact device that had an issue you'd never see minor packet loss in a trace. This is the problem that MTR addresses. You should really use WinMTR over traceroute, it gives more information and data over time instead of the single point in time that traceroute gives. Should be what you see when you first run. Type login.riseofagon.com in the Host box. Then before you hit start, click on Options: Change interval to 0.1, it defaults to 1.0. Click 'OK' and then click 'Start'. Changing this will make it ping every 100 milliseconds which is fast enough to catch quick losses but not too much that the packet rate will cause its own issues. Leave the MTR running throughout a play session. When you get a double swing/ghost swing, alt tab and stop the MTR. Copy the text and paste here. Also for the ping test do yourself a favor and just use ping -t instead of ping -n. It will ping until you stop it with Control-C. If you ping -n 1000 and the ghost swing happens at 1001 seconds then it's useless data.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.254 - 16 | 1743 | 1476 | 0 | 0 | 23 | 0 | | 10.31.154.1 - 1 | 14476 | 14475 | 4 | 12 | 284 | 10 | | NYCMNY83CI01.bb.telus.com - 1 | 14390 | 14387 | 74 | 75 | 129 | 75 | | paix-ny-peer.lga5.us.voxel.net - 1 | 14472 | 14471 | 80 | 81 | 170 | 80 | | bbr1.ae7.nym007.pnap.net - 1 | 14413 | 14411 | 77 | 79 | 173 | 78 | | tsr1.e6-1.nyj004.pnap.net - 1 | 14384 | 14381 | 68 | 76 | 124 | 85 | | 173.231.188.40 - 1 | 14484 | 14483 | 68 | 73 | 118 | 75 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Not sure why I am getting 16% loss to my router.....but everything else seems ok. I kept peeking at this when I was getting anomalies, and the ping was not spiking or anything.
Very nice, i'll have to check out winmtr. I've always had a spotty connection to the server so it will be interesting to see what the culprit is.
Looks like you lost a packet to the login server at some point. Did you do a ping in a separate window at the same time as this? I wonder if it's possible that a single packet lost triggers something in the game client that can cause these issues. That's just a huge guess. For someone at BPG, can we get the IP of the actual game server instead of just the login server to mtr against, even if it's in a PM to only a few folks. I can't get in game to check netstat myself right now. It would be best to test to the actual server that's processing game packets instead of the login server.
I would guess if they gave us the login server to test the connection the server is likely behind the same IP on the same machine. Could be wrong but if funds are tight they likely have a single dedicated. If they had the game server on a separate machine on a different network they likely wouldn't want to give out the IP so ppl couldn't ddos the main arch just the login server.
Maybe, but if you're talking to it via the game client then you can see it in netstat or tcpdump so the ddos part is moot. I just can't login to check it myself right now.
The "login server" is just simply a node running on the game servers, it isn't a separate server in the cluster. It's easier to do the DNS address than the IP in case the IP changes potentially in the future.
Tracing route to login.riseofagon.com [173.231.188.40] over a maximum of 30 hops: 1 4 ms 3 ms 5 ms 192.168.0.1 2 27 ms 16 ms 24 ms 142.254.191.45 3 33 ms 29 ms 32 ms xe-0-0-1.hilohiee02h.hawaii.rr.com [24.25.230.11 7] 4 24 ms 17 ms 18 ms agg41.kmlahi0701r.hawaii.rr.com [72.129.45.58] 5 73 ms 74 ms 69 ms agg31.tustcaft01r.socal.rr.com [72.129.45.2] 6 73 ms 77 ms 79 ms bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.10 9.3.232] 7 70 ms 74 ms 69 ms 0.ae2.pr1.lax10.tbone.rr.com [107.14.19.54] 8 70 ms 79 ms 71 ms las-b21-link.telia.net [62.115.36.57] 9 149 ms 156 ms 149 ms nyk-bb4-link.telia.net [213.155.135.118] 10 148 ms 149 ms 149 ms nyk-b5-link.telia.net [213.155.131.139] 11 148 ms 159 ms 151 ms internap-ic-305784-nyk-b5.c.telia.net [213.248.6 6.102] 12 143 ms 143 ms 147 ms border1-po2-bbnet2.nyj004.pnap.net [216.52.95.10 9] 13 151 ms 154 ms 164 ms 74.201.136.66 14 155 ms 151 ms 153 ms 173.231.188.40 Trace complete.
Please fill out the form linked in the OP to submit the details. It will help to organise the details into a spreadsheet for diagnosing, thanks!
Please move the servers to chicago and revert the texture patch. It will help to increase server stability and client hitches and awful load lag. Thanks!
Just sent you one. I'd strongly suggest recreating that form with a larger maximum character input for ping/trace pastes. My response just barely fit and I had to truncate it multiple times. Just FYI.
