<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Ryan, thanks for the response and thanks for all you've done for CoD!
I didn't mean to fault Activision and IW as much as I did. You're
correct that they have done more for Linux than other's (see EAGames).
Your help has always been superbe. I understand Activision's stand on
support, as with most companies. Being a computer professional, I
NEVER call 800 support numbers if it's a computer releated question.
For someone working in the computer industry, it's futile. They know
less than me, and I'm not going to reinstall Windows to fix my problem.
<span class="moz-smiley-s4"><span> :-P </span></span><br>
<br>
Part of the frustration stems from the original topic of this thread,
the browser issue as well. We've seen the browser numbers fluxuate all
over the place, and a lot of times our server it not on the list, hence
it is empty. We had a full 1.1 server (actually still do), and 1.2 was
empty. The verdict is still out on 1.3. Sometimes it's empty,
sometimes it's full.<br>
<br>
Anyway, thanks to you and IW and Activision for all you help! I really
like CoD, and I think most of us just want to see it get better. I've
programmed, I've debugged, I've done support. I know where you guys
are coming from! I too would be curious what in the Linux binary makes
things shoot right... (Although I'm not looking frorward to another
rount of updating about 30 CoD servers....)<br>
<br>
Maverick<br>
clanselite.com<br>
<br>
Ryan C. Gordon wrote:<br>
<blockquote type="cite" cite="mid1080556851.3795.27.camel@localhost">
<blockquote type="cite">
<pre wrap=""> Sorry, I'll get off my soap box now. :-) Yeah, this touched a
nerve... I like CoD, and I think IW has done a great job, it's just
they need to get serious about Linux.
</pre>
</blockquote>
<pre wrap=""><!---->
Fwiw, Infinity Ward and Activision _are_ really serious about Linux
servers; moreso than most developers (and publishers!) than I've seen.
1.3 for Windows was actually delayed while a Linux server bug was
tracked down, which, when you consider the amount of bile spewed in IW's
direction over the delay in releasing 1.3, this was awfully nice of
them.
The reason the machine-gun-fires-to-the-right bug isn't fixed yet is
because I've been out of town all week at Game Developer Conference. We
didn't find it in QA, so we didn't fix it. I'm tracking it down right
now, and will release an interim binary as soon as I figure out the
problem.
Activision's official line is "we don't support Linux" because they
aren't really staffed to support it. The calls they get are "uh, my
DirectX install is broken", etc. You need to have a full time staff to
deal with this, and they aren't prepared to talk about glibc versions
and CPU usage and such. Quite frankly, for admin issues, you are always
going to be better off talking to other admins. That's not to dodge the
bullet on behalf of Activision, but really, I'd rather ask and answer on
a mailing list like this than sit on hold on some support line. The
brains that make this happen (including the original developers, myself,
and an army of professional server admins) are all here. If I was
running Activision, I would train my support staff to send you here
anyhow, but maybe that's just me.
--ryan.
</pre>
</blockquote>
</body>
</html>