Domain registration expired and for some reason their nags and reminders never made it to me. Back on the air now, sorry about that.

Xamindar wrote:Who is the server admin at Beta.Descent.cx so we can knock him upside the head?

Thanks, but no thanks.

As the server name suggests, I was asked to host the beta test of a new level, not available to the general public. I made it visible on the tracker for the beta testers' convenience.

You need to add you gamespy port(s).

Yes, Munk was generous enough to create a workaround for the checksum bug. It basically uses iptables to substitute "corrected" checksums What an *awesome* hack! I'd love to see the iptables rule for that. do you still have this Perl script? I'm thinking this might be one of the last pieces of the ...

I got it working, but it only seems to work for a little while and then the server doesn't show up on the tracker any more. Is there some reason for this? Yet another Linux D3 bug: the server stops sending hearbeat packets after N minutes. A few years back when I was fighting for this same lost ...

will_kill wrote:Not sure why my e-mail was undeliverable tho'...what addy did I give ya'?

willkill -at- <your cable isp>

and a big ol' WELCOME! is in order...

Thanks, but I've been here a few times before

Somebody here (name withheld to protect the fumblefingered) asked me to host this level, but didn't specify game parameters and had an undeliverable email address.

What's the recommended game type, number of players, respawn, etc?

Thanks [BLUSH]

He could be an even more kickass serverop by running good oldschool levels. :) Try requesting some. ;-) Request link at top right of tracker page. Kata (6 player anarchy) Apparition (8 player anarchy) SLW (6 player anarchy) Pyroglyphic (8 player anarchy) These are up. Email corrections to server ...

FWIW, I am switching from having 2-hour timeouts in the server configs to having D3Server3 restart idle servers every 2 hours.

1.5 megabits up? Easily, as far as bandwidth, CPU, and memory are concerned (you also need good latency.) CPU and bandwidth requirements scale exponentially with the number of players: you would need *more* bandwidth and CPU for a single fully-populated 16-player game than your 8+4+2+2 scenario. A ...

WAN circuit outage due to hurricane Ivan. We're back.

I'm sorry to be the (way belated) bearer of bad news, but the root cause of your Linux D3 woes is the hopelessly buggy state of the Linux D3 server port, and there's nothing you can do about it until [sic] the mythical 1.5 patch comes out. I speak from some battle-hardened experience here. There are ...

WarAdvocat wrote:thanks for the suggestion. I've been using Kquery, not esa's tracker, but I know he browses here so I posted

Yeah, but email to server@descent.cx works better (and faster)

Do_Checkor wrote:Hey esa what do I have to give you to link to www.Descentforum.de ? :p

Your invoice is in the mail.

Speaking of Esa's site, I did a search for something, and guess what popped up in GoogleAds? d3.descent.cx! Esa, did you sign up for that? It really tripped me out. One thing..I don't recall the wording (Tho' I saved the page for reference..at home) saying it was for Descent3. Just "join TCPIP ...

Shadowfury333 wrote:I just tried accessing d3.descent.cx, and I got a general empty domain site. Has Descent.cx called it quits, or did I just type something in worng*.

*besides this

You typed in something worng.

http://d3.descent.cx/ redirects to http://d3.descent.cx/tracker.d3 , either URL will work.

Anarchy? CTF? Other?

Liquid Fire wrote:Yes well, the problem is making the server...See the post about the "minor peons" for further details.

How about clicking on the "Server Request" link at http://d3.descent.cx/ ?

I can be reached at server@descent.cx

30 players is not practical with any amount of CPU or WAN bandwidth, however. A level like Polaris or the Veins variants which keep players and projectiles separated into smaller groups can support 18, perhaps 20 players on a T1 assuming no modem-speed players.

CDN_Merlin wrote:No one listens

To clarify: Mea culpa. My server, accidental omission, now fixed.

Woops

P.S. I finally played Bada Bing....it's really kool, and am looking forward to playing "twilight" if it ever gets hosted. P.S.S. I also notice that some games that are being hosted are never played. Maybe we can get them to host twilight. Bettina. Working on that. But no one is responding. Twilight ...

[nevermind]

Problem fixed.

It simply times the game status query.

The client first requests the list of active games (ones sending heartbeats) from PXO, then queries each one to get player counts.

Upon receiving a heartbeat packet from a server, the tracker submits a game status query to it. I have doubled the timeout of that status query.

If you still have trouble keeping games visible, please contact me via email and I'll check the tracker logs.

Woops: cookie is updated properly but the form isn't populated correctly. The user interface is less than elegant: you have to click the "refresh command line" button to update the cookie. I'll see if I can stretch my HTML authoring skills to store last N pilot names and present them as a dropdown ...

Suncho wrote:Actually that takes longer because you have to enter your D3 path, command line options, and pilot name every time.

Whoa! Not if you accept the cookie.

I'm using D3Server2 BTW. It should be a breeze with D3Server2: 1. Check the "Use game trackers" checkbox under each server configuration 2. In the dialog box that opens, check "Descent.cx" 3. Permit the game tracker port (20142 by default, but must be different for each server if you're running ...

Yes, random respawn everywhere. Guidelines and suggestions welcome for min/max.

Sorry, didn't mean to imply so much drama and intrigue. It was just a buglet in D3Server3, already caught and squashed by (DE)Hunter.

Why am I prohibited from switching now (see, e.g., D1.Descent.cx -- Monsterball Mayhem)? It just seems ... wrong, but I allow for the possibility there's something else at work here. Something else is indeed at work here. Fix/workaround has been put in place for Descent.CX servers. Thanks for your ...

D3DSN rocks, but has a few buglets remaining.

In the meantime, your 5-player skybox is up as WarAdvocat.Descent.cx.