Crash After Server Select

E

elr0g

Dalayan Beginner
Heya.

So, after doing several searches through these forums (and on google), it seem as if this is, or at least was, a very common problem. The problem I am having is exactly what many people on the thread http://www.shardsofdalaya.com/forum/index.php?topic=4943.0 (as well as many other threads) describe. I can patch fine, enter my username and password fine, and see the server list fine. However, whenever I try to advance to the character select screen (by either clicking the button or pressing enter), the game hangs for about 15 seconds looking like its trying to change resolution and then quits back to the original splash screen that you see right after agreeing to the EULA.

I could post my dbg.txt file, but it really is the exact same (in all important respects) as the file posted on the aforementioned thread.

I should also note that this started happening the day after the most recent server-side patch, though that is probably a coincidence as I could log in the day of the patch after the patch occurred (just not the next day). [Bleh, that sentance is worded awkwardly... hopefully you get the gist.] Also, when I could log in, doing so was very flaky. I would have to try to log in ~10 times before a successful attempt (on unsuccessful attempts the same thing that is always happening now would happen: exit to the first splash screen without any error message).

As for what I have attempted: pretty much everything that I have control over. Re-installed the Game, ran many hardware diagnostics, locked the pixel pipelines and vertex shaders that I had unlocked on my geforce 6800, under-clocked my video-card, tried installing the game on different hard-disks, etc., etc., etc. I even wanted to play one day so bad I set up cedega on a Ubuntu 6.10 (edgy) partition on this computer and tried to run "the game" from there. Lo and behold... exact same problem.

So, bleh. That being said, I really highly doubt anyone can help. It sounds like this is not an uncommon issue and I have not seen any solutions to it. However, with the few searches that I did on these forums, it doesn't look like anyone has posted this problem for the past several months. Does that mean a solution has been found?

I really want to play on this server, I would even be receptive to extreme suggestions that sound reasonable. I liked this server so much that after only like a week of playing I decided to start donating. The funniest part is that the day after I signed up for the donation is when the problems started occuring. My only conclusion to this whole mess of a problem is that god hates me.

Oh well... Again, I would be highly receptive to any suggestions.

Thanks in advance,
elrog

EDIT: Oh yeah, I forgot to mention that I am not behind a router per se. I get free internet access via my apartment, so I connect to one of their routers. I have no idea what the network topology is like, but I also don't have control over it. If this issue didn't persist intermittently before, I would swear that it is a network shaping problem. As is though, it really doesn't feel like it to me. I can also access the game's live servers fine. *shrug*
 
I had this issue the other day, although I was using a Westell Modem connected to my Lynksy router. I had enabled IP passthrough and targeted my router, and I had DMZed my computer because BF 2142 takes up too many port forward slots, to the point that it can't even fit. Instead I configured my ports on the Westell Modem. =P

Well I disabled the IP passthrough, rebooted the modem and released/renewed my connection. It fixed the problem. =D
 
I semi-skimmed that, but yes crashing after sever select is very common, I expect to crash 0-2 times when I load up the game. Things that might help alleviate it which I have seen:

1. Turning off anti-virus (this also helps tremendously with client side lag if you're running two clients)
2. Minimize the number of other programs running, especially ones using bandwidth (if I'm running bit torrent or ventrilo, that can bog it down)
3. Don't switch "attention" from the client's screen after you hit enter to join the server, aka don't alt tab off of it until it starts the loading screen

Hope that helps a little.
 
Try to use less router resources. IE switch off your Bittorrent download or any file download when you hit play.
It helps
 
OK, so following several days of never being able to log on, my internet completely died for several days. During which time I have been told that the router was rebooted. (I also learned that the router I am plugged into is not part of the apartment complex, it is an extremely large router owned by my ISP. So, I am essentially directly connected to the internet.) Now I can just play completely sporadically; I can try to log on 15+ times unsuccessfully but if I try an hour or so later it will connect.

I noticed 2 things, though, that I was wondering if anyone else that is having this problem has also noticed:

1) The longer it takes to "Establash a connection with the login server" (immediately after I enter my password), the less likely it is that I will be able to actually enter the server. Moreover, whenever the "Establishing connection with login server" only briefly flashes before it says "Login request added to queue... please wait..." I have been able to actually log on.

2) Network latency does not seem to affect my chances of logging on. I ping ~40 to the the Game server (whose IP was found using netstat) pretty much all the time. That is, I have been able to log on while my ping is ~40 and I have been unable to log on when my ping is ~40. (And this is always on a freshly rebooted computer only running system critical background processes. In linux as well as windows. Always immediately after I repatched the Game using the Game.exe and then sodpatcher.exe and deleted all ini files that seem relevant.)

Now, these two things seem at odds to me. It seems to suggest to me that this is more a server-side problem than a client-side problem. Does anyone know if things like timeout settings have ever been played with on the server? Maybe it has absolutely nothing to do with the current problem, but its really the only thing that I could think would be causing this. Or, perhaps, can anyone think of any other diagnostic measures to take?

(Oh, and I have tried all of the things suggested so far. Has anyone had any success with anything wackier?)

Again, any input is appreciated.

-elrog

Ack, I just read on another thread that timeout time is hardcoded into the client. Oh well...
 
You must log in or register to reply here.
Back
Top Bottom