Ns Causes Broadband Lockup?!?
jedistud
Join Date: 2003-08-04 Member: 18879Members
in Tech Support
<div class="IPBDescription">similar to popular v2.0 crash issue...</div> First of all, I also have the gamma issue. Sometimes when I click on a server to play (through v2.0, not gamespy), the game closes out and the gamma is fried. Only solution is to restart.
Main problem: I am still trying to determine whether I'm doing something in particular, but I don't think I am. I am simply playing and the game locks up as if the server crashed. I eventually get the "warning: connection problem" message. Most of the times, I can still hit 'esc' and end the current game. However, I've completely lost my connection to the net. I can't join any other games, and when I quit the game, I can't even surf the web. Restart is the only solution. I don't think this happened the first couple of times I played v2.0, but its happened every time since. This has NEVER happened to me before.
-P4 Dell Inspiron 8200 (yes, I play on my laptop)
-384 megs ram
-WinXP
-nVidia Go 64 megs
-crystal wavetable soundcard?
-1600x1200 Dell Ultrasharp (but play at 1024x768 OpenGL - gamma is maxed out)
-Motorola Surfboard
-comcast broadband
-Current HL retail (1.1.1.0 maybe?)
-NS v2.0
Main problem: I am still trying to determine whether I'm doing something in particular, but I don't think I am. I am simply playing and the game locks up as if the server crashed. I eventually get the "warning: connection problem" message. Most of the times, I can still hit 'esc' and end the current game. However, I've completely lost my connection to the net. I can't join any other games, and when I quit the game, I can't even surf the web. Restart is the only solution. I don't think this happened the first couple of times I played v2.0, but its happened every time since. This has NEVER happened to me before.
-P4 Dell Inspiron 8200 (yes, I play on my laptop)
-384 megs ram
-WinXP
-nVidia Go 64 megs
-crystal wavetable soundcard?
-1600x1200 Dell Ultrasharp (but play at 1024x768 OpenGL - gamma is maxed out)
-Motorola Surfboard
-comcast broadband
-Current HL retail (1.1.1.0 maybe?)
-NS v2.0
Comments
Go to your Natural Selection folder (mine is C:\Sierra\Half-Life\ns). There should be a file called 'Resetgamma', make a shortcut to it. Now whenever you game crashes and the gamma is messed up double-click this shortcut. The gamma should be fine again.
EDIT: I just noticed that you have the same broadband modem as me. When my internet buggers up I tend to unplug the modem for 20-30 seconds (no less, has no effect) and plug it back in. Once the four green lights come back on the internet is usually fine again. Just make sure it's not in stand-by mode, I've been caught out by the problem several times.
If you cant get a new modem then I find switching everything off and restarting is the only solution.
I think its a modem prob rather than an NS prob, and my situation only got worse, it would cut out for 10 hours at a time, and restarting didn't fix anything.
It doesn't seem like others are having similar problems, so I'm going to go back tonight and see if its still happening. Maybe comcast was upgrading the network or something.
I have a feeling its tied into this Windows crash thingy other people have been experiencing...
The fact that you were able to play 2.0 for, what a day? before this started up leads me to think this.
The think o do is contact your ISP. I have gotten similar problems like this many times, and there are a few possible things (you ISP should be able to fix you up).
Why I think this is not a 2.0 prob is simply enugh it COULDN'T be, I meen HL simply dosn't have that much effect on your comp to screw you up that much.
Ok, just a quick thing you might wana try:
When this happens and you can get to windows simply kill your net work connection (Start-->Settings-->Controll Panell-->Network And Dial-Up Conections)
reboot you MODEM (either via a button or simply pulling the power) wait a few secs, plug it back in and start the network again.
Even if this does work CONTACT YOUR ISP IT WILL WORK!
but this never happened with cs/or 1.0....