Old player, is back lol
First ,i want to thank all that have kept this game running , Thanks for the great work and for your precious time. I have installed the game on two PC, one is running great after many UE errors i installed the (irc fix), however on the other-one i get UE error after logging in, once i try to join a server it crashes, theres only one server that the games does not crash, so i mosey play on that . anything i can do to fix this thing, would like to try other servers. Thanks😀
Comments
I'd need the memory addresses from unhandled exceptions to be able to diagnose or write fixes – without them it's mostly guesswork from context clues. I assume you have the IRC fix you have was the general fix I'd done for WinSock DNS lookup failures, which is probably the most common crash since some old scripts attempt to connect to sites long gone, although this wouldn't affect joining servers.
Do you have an unusual network setup on the one device? If you open your console (~) and enter
echo($IPv4::InetAddress);does it match what's reported on https://ms2.tribesnext.com/whatismyip or elsewhere for your expected external IP address? This variable is used in communication with servers to detect snooping and may cause issues on repeat connection attempts if not set to the IPv4 address the server sees you connecting from.OK i checked the IP address and it is correct IP address , this is what the error is : Unhandled exception: c0000005 At address: 00583973
Hope it makes sense, thanks for your reapply :)
Ok, so I haven't thought about this one for years, but the error you received there is the game attempting to process a queued up network event that doesn't exist - the current list was corrupted somehow, possibly because the event was deleted early or invalid data was inserted. Are the two devices on the same network, running with basically the same setup?
Could you be trying to reconnect quickly to a server while it's still sending you packets from a prior connection attempt?
The IPv4 mechanism I mentioned before could lead to this on unusual networks (cellular, proxies, VPNs, etc) where if it detects an irregularity in the address the server reports back, it will disconnect from the server from the client side (and sometimes the error message may not be shown) – meanwhile, in the background there's still a packet or two being communicated between you and the server to close out the connection. Reconnecting immediately has in the past caused a few people to crash this way... In most cases you can resolve this by making sure the external address is getting set correctly, but it's technically possible to strip the ipv4 verification out of the client side of the authentication script if necessary.