The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: <ron@ronnatalie.com>
To: <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Gaming on early Unix
Date: Fri, 6 Dec 2019 11:19:12 -0500	[thread overview]
Message-ID: <22df01d5ac50$eca8e330$c5faa990$@ronnatalie.com> (raw)
In-Reply-To: <ltHJoDDEOs5-xEO89I41fL1EtqGSVAQBplC23ejqb4QSevDcIaP-Iu-SEf66ZXYoTZfwcHe_CF9JwJ_Ypdj_qpazTGhqo7feaGau_POndD4=@qswarm.com>

[-- Attachment #1: Type: text/plain, Size: 2891 bytes --]

We were big into “Adventure” when I first started on UNIX.    It wasn’t until someone handed me the Fortran source code did I find we had missed a few things in it (like the rusty rods with black stars).

 

Rogue was a popular one later.   

 

Later at BRL we got a copy of “Empire” from PSL.   The good thing about that game was that your amount of activity was limited to one hour a day and however many BTUs (Bureaucratic Time Units) your capital generated.    However, people would print maps near the end of their session and then spend hours planning the next day’s activity.   Finally, the lab management had us shutdown.

 

There was another multiplayer game called “Search” that would result around 4:30 in the afternoon someone yelling “Search Up” which was everybody’s cue to join in the game.

 

Then we got SGI workstations.   The flight simulator had a dogfight feature but it used some networking that didn’t work on our network (I think it was XNS broadcasts).   Fortunately, the source code was available so I hacked it to communicate via TCP/IP to a central server (which had its own “air traffic control” display for my own benefit).    At 4:30 everybody would head off to an SGI workstation and we’d have many people flying.

We had the problem of people hanging out around the runway (where new players appeared) and nailing people as soon as they showed up.   I wrote an automated “anti-aircraft gun” that shot at people who hung out around the airfield.

 

I was at a meeting (probably IETF) and the NASA AMES guys (who had tons of these workstations as well) found out about my work and made me FTP it to them right then and there.    There went NASA productivity.

 

BRL had a vector graphics system in the early days called a Vector General.   They were left over from a project with the Cyber mainframe that never worked.   The labs had three or four of these things, each a PDP-11/34 with the Vector General, a card reader, a printer, a DQ-11, and a 50K modem.   At a loss for what to do with them, we put UNIX on them.   Mike used the system to develop the BRL CAD package.    The printers got used for other purposes.   The card readers pretty much were trashed but we kept one to convert old COMGEOM decks.   We actually used the DQ-11/50K modem things to extend the BRLNet (and ultimately the BRL gateways).

One evening, Mike and I decided to write a game for the thing.    We decided to simulate the “Asterioids” arcade game.   Mike did the graphics work and I wrote the game logic.    We spent all night writing it and then went home in the morning leaving it running.     By the time we came in later in the day, several of the BRL researchers (physicists and aerodynamics guys) had hacked on the game logic to make it more realistic (conservation of momentum and all that).

 


[-- Attachment #2: Type: text/html, Size: 5047 bytes --]

  parent reply	other threads:[~2019-12-06 16:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 10:45 Gabriel Diaz
2019-12-06 11:01 ` Steve Nickolas
2019-12-06 14:23 ` A. P. Garcia
2019-12-06 14:48   ` A. P. Garcia
2019-12-08  7:48   ` arnold
2019-12-08 19:54     ` Clem Cole
2019-12-06 16:19 ` ron [this message]
2019-12-06 16:39   ` Richard Salz
2019-12-06 16:54     ` Dan Cross
2019-12-09  0:05     ` Steve Johnson
2019-12-09  0:35       ` Ken Thompson via TUHS
2019-12-09  0:46         ` Adam Thornton
2019-12-09  2:03           ` Rob Pike
2019-12-09  2:10             ` Ken Thompson via TUHS
2019-12-09  2:15               ` Rob Pike
2019-12-09  2:19                 ` Ken Thompson via TUHS
2019-12-09  8:41                   ` Gabriel Diaz
2019-12-09 11:17               ` Angelo Papenhoff
2019-12-09  8:40         ` Naveen Nathan
2019-12-06 17:24   ` Arthur Krewat
2019-12-06 17:58   ` Dr Iain Maoileoin
2019-12-06 22:12     ` ron
2019-12-07  0:04       ` Rob Pike
2019-12-07  1:22 ` Adam Thornton
2019-12-07  1:28   ` Adam Thornton
2019-12-10  0:30 Doug McIlroy
2019-12-10  5:08 ` Adam Thornton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='22df01d5ac50$eca8e330$c5faa990$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).