Re: Quake 2 Summer 1997????

Article View: alt.games.quake2

Article #95

#95

From: Jean Paul Ladue
Date: Fri, 27 Jun 1997 00:00

30 lines
1752 bytes

	I just got done reading some updates to John Carmack's .plan, he states in
one update that everything is on schedule (no shit!), and the next update
says, nobody is going to eclipse Quake 2 this christmas.  So how does this
christmas translate into mid 98'?

PhiberOptik <nob...@nowhere.com> wrote in article
<01bc7f3a$12732ce0$d421aace@zed>...
> Totally bogus. I work for a major gaming software developer and the word
is
> that id is shooting for mid 98'. dont be shocked...the inter company
motto
> for Quake2 has become "When its done" wich pretty much speaks for
> everything else id has put out.
>  
> Since Quake2 will use a different graphics engine that Quake1, its not
> surprising that its taking so long. Carmack wont publish anything hes not
> happy with and I dont blame him. I will never have one of my engines
become
> shovelware. Ever. Ive learned to expect great things from id and I am
> confident that Q2 will be verything Q1 was and more. Ill mail around and
> see what else I can dig up. More on this later....
> 
> Once Bitten (john) <Fa...@any.org> wrote in article
> <33a6a05b...@news.erols.com>...
> > The latest issue of PCGammer lists the release date for Quake 2 as
> > Summer 97.  Last I heard it was to be released in December 1997.  Is
> > this an error in PCGammer??
> > 
>

Technical Details

Message-ID: <01bc82c1$3846e300$3ad2c3d0@stargate.sgi.net>

Path: mbox-mo1.pugleaf.net!unknown!not-for-mail

References: <33a6a05b.2408241@news.erols.com> <01bc7f3a$12732ce0$d421aace@zed>

Show Full Headers

Complete Article Headers

From: "Jean Paul Ladue" <jpl...@telerama.lm.com>
Subject: Re: Quake 2 Summer 1997????
Date: 1997/06/27
Message-ID: <01bc82c1$3846e300$3ad2c3d0@stargate.sgi.net>
X-Deja-AN: 253285820
References: <33a6a05b.2408241@news.erols.com> <01bc7f3a$12732ce0$d421aace@zed>
Organization: None
Newsgroups: alt.games.quake2
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Reply to Parent Message