The dreaded clock...

[charlesk]

Hi everyone...

I'm new to Nexuiz (and FPS in general) and have been enjoying playing... except that I keep running into a problem.

Playing locally on my own server works fine, but whenever I connect to a net server, I get "hyper lag" -- a clock shows up on the screen and stays for up to a minute or even longer. It's completely random as to how often this happens, and it occurs even when I am otherwise experiencing no lag.

There are actually a couple of PCs here that both do this. And while the clock is there, other net functions work okay.

I believe my wireless router may be responsible, because when I connect straight to the cable modem it doesn't appear to exhibit the problem. Unfortunately this is not a practical option, especially since Nexuiz is the only app I have that is behaving oddly.

I have discovered that the best way to "wake up" Nexuiz is to try to click "Join'.. when it is locked then no servers will appear, but if I alt-Tab to another app and then go back to Nexuiz again, the list will populate and the clock will go away.

Anyhow.. I am wondering if there is possibly a more efficient way of "waking up" the game.. or if there is anything I can try in its configuration to solve this problem. Thanks for your assistance.

c

[esteel]

Can you tell us what router you have? It seems to NOT behave nicely
Do you also use WLAN for playing or is it just that your router is also wlan capable? Playing via WLAN can be bad, as WLAN is often highly sensible. If thats the case maybe using normal cables for you network already helps.

But it might also be your router itself. 'Normal' Applications only use short connections.. getting a small page from the net, an small image inside it.. But gaming uses the SAME connection for a few long time. Maybe your router does change the ports during NAT after a while. If thats the case it could help to tell Nexuiz to use a static port (cl_port NUMBER) (default 0 = random) and also to tell your router to forward that specific port to your computer. that should prevent it from doing 'stupid' stuff.

[charlesk]

Hey there esteel.... thanks for the reply.

Can you tell us what router you have? It seems to NOT behave nicely

It's a Linksys WRT54GP2 with VOIP.

Do you also use WLAN for playing or is it just that your router is also wlan capable? Playing via WLAN can be bad, as WLAN is often highly sensible. If thats the case maybe using normal cables for you network already helps.

My PC is connected by cable; my son's by WLAN. I tried disabling the WLAN in the router setup and that didn't help.

But it might also be your router itself. 'Normal' Applications only use short connections.. getting a small page from the net, an small image inside it.. But gaming uses the SAME connection for a few long time. Maybe your router does change the ports during NAT after a while. If thats the case it could help to tell Nexuiz to use a static port (cl_port NUMBER) (default 0 = random) and also to tell your router to forward that specific port to your computer. that should prevent it from doing 'stupid' stuff.

Hmm. I guess I could look into this, though I am not sure exactly how I would do so.

I have no problem with, for example, very long downloads, or even FTPing up or down 250 MB files. Nexuiz seems to be the only thing that I have trouble with.

Do you know of any console command that can be used to make the game refresh its net connections or similar?

Thanks. --c

[torus]

I had the exact same problem, and when I switched routers, it disappeared.
Mine was a Linksys BEFSR41v2.

[charlesk]

Thanks for the data point.

Of course, spending $100 on a new router to play a game I got because it was free doesn't make a lot of sense.

c

[divVerent]

Well, port forwarding + cl_port should provide quite some chance to make it work.

[charlesk]

Wow.. I think the port forwarding may actually have worked! Still need to test a bit more though. Thanks!

How do I tell Nexuiz always to use the same cl_port automatically?

[divVerent]

You can write the line

cl_port 26005

or like that in a file called autoexec.cfg that is put next to your config.cfg (in the data folder).

[charlesk]

Hmm, that didn't seem to work.

[esteel]

It should.. are you sure you used a file Nexuiz\data\autoexec.cfg und put in the right cl_port number? Also entering seta cl_port xxxx should cause it to be saved to config.cfg. Make sure you use the right number for both the variable and the forwarding.