Several times today (and always during a fight), the client would stop responding. Damage indication would continue after my ship exploded. I would never get passed this point without having to Esc/logout.

Note, my ping was always between 50 & 65, fsp over 50.

I was in a tournament, in a hurry, so i didn't check the logs until the forth time it happened. The following was in the files following these events:

[wtf? I just sent seq 202(2;try#1;AS len 25) after 138(3;try#8;aS len 75).]

and again later:

[wtf? I just sent seq 23(3;try#1;AS len 4) after 213(1;try#8;as len 75).]

(XP system, network config unknown)

"[wtf?..." has [X]Andy written all over it. Don't worry, with his little error messages, he'll have it fixed in no time.

Heh, those 'wtf' messages are actually not indicating a problem per se, although it does seem that you had excessive packet loss and the network code was stalled as a result. But that could also be caused by loading the station interface or something, as the network code isn't threaded and gets stalled while the client loads stuff.

Can you explain what you mean by "the client would stop responding"? You're in a fight, your ship explodes, you see the animation, and you still see red flashes? And you don't warp to the station, you just sit in space?

Exactly.And it only happens during fights. During a duel, everything working fine until a minute or so (sometimes less) into the fight. At some point, from my perspective, my opponenent would go elsewhere, firing, and I would begin to take damage from his shots. The animation continued, similar to timing out from the server, but I could still see the channel, mission chat and sector animation. If they became aware and stopped firing, this is how things would remain until I logged out. If it were bots, when the ship finally exploded, I would not warp to the station. The red flashes, sector animation, all continued to update. Once I was even able to send PM's to another player.

For anyone elses perspective, I would just be spinning in space or just gone.

Today, however, I logged on and had no problem at all.

Happened again today, against 5 Un-bots in B8.

"wtf? I just sent seq 1(1;try#1;AS len 8) after 190(purged)."

Try setting the only network option (MTU discovery) to "compatibility mode" and see if that helps.

still happens... just no "wft" messages.