A few weeks ago, when I first got mudfish, my connection was very spotty to the game server with commonly lost packets. After I began using mudfish, the packet loss almost entirely disappeared, but I’ve been losing packets again no matter what nodes I use. Is there a way that I can dose? Is this a local network issue with my computer or hardware? Is it an isp/local backbone issue? Mudfish issue? Game server issue?
Did you try to change a mudfish node based on FAQ - Nodes section for your game item? If you’re using the advanced mode, please start with the basic mode.
Hi, yes, I’ve made sure my game item is configured correctly. In this order, I’ve tried the following:
Using single node with overall lowest score: occasional packet loss
where I lose connection on my game client for 5-10 consecutive seconds.
-
Using single node with lower std but higher rtt: same issue as above, but not happening as often.
-
2 nodes that have a higher score than single node: same issue as 1, but with the issue happening just as frequently.
This is what I’m currently using and I’ve seem to had the best luck
with this set up so far. I advanced node and find best set up for me
-> node, which is las vegas node of lowest score, then I find best
server with best score node -> game. I put these two in advanced
mode. This has been the most reliable so far, but still not perfect.
What’s
odd is that a month ago, I wasn’t having any issues even without
Mudfish. I don’t know what changed so drastically from then to now to
make my connection be such an issue!
If I remember correctly, there’s still nothing changed at Mudfish side. And please check ‘Status -> Nodes’ menu to see your RTT avg and stddev between your desktop and mudfish nodes. Sometimes your ISP could cause this issue but we need to check it first. If you’re famliar with WinMTR I think you can analyze this issue little bit more.
Well, I’ve actually discovered it’s a widespread issue for FF14 that a
lot of people are having. It seems specific to NTT nodes near the actual
game server, which explains why there’s still packet loss sometimes
even through Mudfish. I found this reddit post today:
https://www.reddit.com/r/ffxiv/comments/7pealb/dropped_packets_result_in_highly_unstable/
I’ve uploaded a couple of results using WinMTR and looks like the packet drops are happening there. Screenshots included below.
If
that’s the case, then the question becomes how to avoid these
problematic nodes, if even possible? I may try some different configs to
see if I can get around those nodes by entering from a different
direction. Even if it means having a higher ping, because frankly, it’s
the packet loss that’s a killer, not the latency.
Thank you for sending this WinMRT result. When I checked your issue, I think you should solve the packet loss at Hop #2 (10.67.128.1). I think it’s your ISP side but in my opinion, it’s meaningless to analyze the further hops (routers) after Hop #2 because your packet loss is started at that point.
So the packet loss rate of Hop 2 affects the packet loss rate of the last mile.
Well, the strange thing I’ve found is that my stability for the first
couple of hops is profoundly better when using Mudfish. See the attached
screenshot below where the first few nodes from my network are now
closer to .1-.3% rather than 1-2%. Am I concluding it correctly that
using Mudfish is allowing me to bypass some troubled connection steps
closer on my end? Or is it just a coincidence?
Well, the strange thing I’ve found is that my stability for the first
couple of hops is profoundly better when using Mudfish.
Only I can guess is Connection Protocols difference but normally Mudfish doesn’t affect or change your RTT within your ISP.
Am I concluding it correctly that
using Mudfish is allowing me to bypass some troubled connection steps
closer on my end?
Nop for your ISP. Mudfish is normally used to optimize the middle miles but not the last miles. ![]()