Connection Issues

[Sydius]

Note that this is with the binary compiled from the code currently in the CVS, along with Xuri's default scripts.

Anyone can connect to my shard and verify their account, but as soon as they try to either create a character or play a character, it sends a random number of packets and then stops all communication, giving the appearance of lagging out.

When I say it sends a random number of packets, I know that because I will get the welcome messages and the tip of the day sometimes, and other times, I will not. Sometimes I will get the system messages, sometimes I will not.

Another oddity is that when the player attempts to move, the move seems successful from the server's perspective because the next time I log in, I am in the new coordinate, though from the client's perspective, it just lags and freezes up. Oh, and the skin is always white with no clothing, items, or any NPCs on the screen.

HOWEVER, when I log on locally (127.0.0.1), everything is fine.

I also got it to work for everybody briefly, but I do not know how, and as soon as I restarted the server, it no longer worked.

I am behind a NAT router, and I forwarded port 2593, which is the port I sat to use.

Xuri verified all of the above by trying to log into the server last night.

It *may* have something to do with the spawned world or something, since that seems to be the only difference between me and Xuri's setup, and I could connect to his fine. Though, I think I checked this, and it still did not work.

Anyhoo, I do not think it is a router issue entirely since people can clearly connect, verify their password, select a server, and then select a character, and even see the game world and get some packets sent at that time.

Additionally, I tested LoneWolf on the same port without modifying my router at all, and everything works great, including having someone at a remote location log in and run around.

[Xuri]

The "skin is white with no clothing, and no items/chars on screen"-problem can be worked around by using the 'REFRESH command (also available to normal players - teleports them to their current location).

The general connectivity problem is worse. It's really puts your spirit down when those kinds of bugs occur - there seem to be no logical explanation for it and it can't even be reproduced on other computers (seeing as how it works mine, using the exact same .exe and scripts).

[Sydius]

They are white with no clothing because no packets reach the client after the initial burst upon login. So, refresh does not work, either.

My computer is dual-core, could that have an affect?

I know a lot of multi-threaded programs work fine until you try to use them on a system that can actually run the threads concurrently. I cannot even play Lineage 2 all that well because of this, heh. They just tell me that dual-core is not supported yet.

I know UOX3 is multi-threaded, and I believe the packet handling is separated from the other threads. Could it simply be a case of synchronization between the threads?

[Sydius]

Tonight, when I get home, I will try to run UOX3 exclusively on one core, and see if that fixes things.

The one time it worked might have been simply because all the threads happened to load on the same core.

[Xuri]

Hm. Whenever I have experienced the "grey/white skin" problem (included no items/chars showing up onscreen after logging in), it's always been "fixable" using either 'refresh or 'resend.. which should be just about the same command

[Sydius]

Hm. Whenever I have experienced the "grey/white skin" problem (included no items/chars showing up onscreen after logging in), it's always been "fixable" using either 'refresh or 'resend.. which should be just about the same command

I said, after a few packets, the client does not receive any more. Period. No matter what. Sure, I can send that command, but the client will not receive a response. The server receives the command, though.