Currently using Mudfish 5.2.0 for Archeage NA. Most server nodes will have varying amounts of packet loss from 1 - 15% and when selecting a node with 0 will soon experience packet loss shortly after. Playing with fast connect mode and using basic node selection.
I had the same problem as yours. But I got it fixed by changing the MTU size in mud fish. Before default it was 1300 after changing it to 1350 packet data loss gone.
Its been 6 hours since I changed the MTU size and this seems to have fixed my packet loss problem. Thank you for your solution and help.
Sadly the MTU change worked initially but the packet loss issue is persisting. Any other fixes?
@JJfever1 Could you please tell me your mudfish ID? It seems your username JJfever1 isn’t found on our system. I need to check your RTT information to analyze this issue.
my mudfish ID is JJfever. I’m not sure why the 1 was added after the migration to the new forums
@JJfever1 Thank you for information. When I checked your account for RTT, it seems your ISP is stable. So at least your ISP looks fine to me. And I noticed that you enabled FastConnect mode and uses TCP protocol for Connection Protocols. Is it what options you used to with Mudfish?
That is correct. When I first used FastConnect the default was with UDP protocol, but I soon switched to TCP because UDP would lose connection when large scale activities in Archeage occurred. Also been using these settings since I got Mudfish 9 months ago and haven’t had any of these issues until now.
Edit: If it helps any the error code I get when the packet loss rate occurs is MUDEC_00238
Hello,
Since my problem hasn’t gone away I have uploaded a packet dump for you through the program. I’m sorry that I am unsure on how to approach this problem further
If you feel your connection seems it’s unstable. Please check How to use WinMTR and test to 208.94.26.44 IP (game server). I think this tool could show where this packet dump is from.
I don’t know if I’ve done this test right but these were the results I got following the instructions of the how to page.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 1421 | 1421 | 0 | 0 | 26 | 0 |
| oki-103-13-250-209.glbb.ne.jp - 0 | 1421 | 1421 | 2 | 2 | 21 | 2 |
| oki-103-13-250-210.glbb.ne.jp - 0 | 1421 | 1421 | 2 | 3 | 21 | 3 |
| oki-103-13-250-218.glbb.ne.jp - 0 | 1421 | 1421 | 30 | 34 | 82 | 46 |
| v223.core1.tyo1.he.net - 0 | 1421 | 1421 | 30 | 30 | 52 | 31 |
| 100ge8-2.core1.lax2.he.net - 0 | 1421 | 1421 | 137 | 142 | 299 | 152 |
| 100ge8-2.core1.phx2.he.net - 0 | 1421 | 1421 | 145 | 147 | 302 | 162 |
| 100ge10-1.core1.dal1.he.net - 0 | 1421 | 1421 | 164 | 169 | 225 | 173 |
| de-cix.dfw.packet.net - 1 | 1402 | 1397 | 165 | 169 | 269 | 173 |
| 0.ae21.dsr1.dfw2.packet.net - 1 | 1406 | 1402 | 169 | 184 | 252 | 204 |
| 198.16.6.54 - 1 | 1397 | 1391 | 167 | 185 | 307 | 184 |
| 139.178.80.103 - 0 | 1421 | 1421 | 165 | 167 | 196 | 176 |
| 208.94.26.44 - 1 | 1413 | 1411 | 164 | 165 | 191 | 165 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)@JJfever1 Thank you for the result of WinMTR. As you can see %1 packet loss is starting at “de-cix.dfw.packet.net” host. And at least I don’t think this issue is from your ISP. It seems de-cix.dfw.packet.net is more closert to the game server network.
No idea whether there’s a routing path to bypass this area. But if not it’s not easy to prevent this packet loss issue.
@weongyo Thank you for your analysis of the WinMTR. The Archeage North America server is located in Dallas where the host is beginning the packet loss. Is this problem the result of a changed routing path by the company that runs Archeage? Before I took a long trip, at the beginning of December, the packet loss never occurred and more nodes had lower RTT scores.
Hello,
Just an update that I seemed to have solved a majority of the packet loss problem by performing a clean uninstall and reinstall of Mudfish. Some slight hiccups occur but I think it’s due to the de-cix.dfw.packet.net host but much less noticeable after the reinstall.
Good to hear that it’s better than before though it’s not clear to me why this issue was happened.
Even though it’s better than before is there any fix to the packet loss that occurs to the game server to rid it completely? Thank you for your help
I’ve actually been having the same issue lately, but with Final Fantasy XIV instead of Archeage. I’ve tried different nodes, tried reinstalling Mudfish, and tried adding an exception for every .exe in the Mudfish folder to my Windows firewall, antivirus, and antimalware programs. It doesn’t happen all the time, but at least a couple times a day. If I leave Mudfish running for a while and connected (as I tend to do), the next time I open the Mudfish dashboard page I’ll be greeted by sometimes dozens of warning and error messages about packet loss, ranging from like 1 to 4%.