Tremulous Crashing For Users on Same Network

[Wootsicle]

Hey,

I don't know if this is an isolated problem, or if it has something to do with the IP address of the user's, but when I run Tremulous, and my friend does on his computer at my house (same router), it crashes the second player to join if we join the same server. It works for a good 30 seconds, maybe even longer, but eventually Tremulous encounters a problem and must be shut down.

Any known way around this?

[kevlarman]

this only happens when you join the same server? it's probably a crappy NAT implementation on your router. you can try to work around it by starting one of the clients with +set net_qport 1234 (or anything that isn't 30720)

[Wootsicle]

Not to sound so nooby, but how does one actually do this?

[Death On Ice]

Use a dedicated server. Don't create from inside Tremulous. (For example, don't click "Play", then "Create Server" to create your server)

[Caveman]

DOI... they are talking about the client not the server...

[kevlarman]

Use a dedicated server. Don't create from inside Tremulous. (For example, don't click "Play", then "Create Server" to create your server)

um yeah, completely unrelated.

[Wootsicle]

Yes, but still, how do I run Tremulous with this setting?

[Taiyo.uk]

You can do it as kevlarman said, or by issuing the command "/set net_qport 1234" in the console before you connect.

[Wootsicle]

"net qport is write protected"

Hrumph.

[kevlarman]

tremulous.exe +set net_qport 1234