Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!zephyr.ens.tek.com!tektronix!sequent!cseaman
From: cseaman@sequent.UUCP (Chris "I'm Outta Here, Man!" Seaman)
Newsgroups: comp.sys.amiga
Subject: Re: Game vs Multitasking
Message-ID: <36361@sequent.UUCP>
Date: 7 Jun 90 20:51:32 GMT
References: <9006010158.AA01507@jade.berkeley.edu> <18302@well.sf.ca.us> <18368@well.sf.ca.us>
Organization: Sequent Computer Systems, Beaverton, OR
Lines: 59

farren@well.sf.ca.us (Mike Farren) writes:
< deven@rpi.edu (Deven T. Corzine) writes:
< >The key is to think ahead.  If you can run an application on a 512K
< >machine, all the better.  [what about the original 256K A1000?  ;-)]
< >However, it is a poor idea indeed to *assume* the configuration of the
< >least common denominator...
< 
< You *assume* that you will be running on a minimal configuration.  You
< then *check* to see if your assumptions are wrong.  Where you find extra
< capability, you can use it, but making the assumption that those extra
< features will be there is dumb - unless your application specifically
< demands it.

The problem here is that many (most? ALL?) game developers seem to be
assuming the minimum configuration, and never bothering to check for
more.  Many, in fact, are apparently presuming that there is *nothing*
else out there.  A perfect example is Shufflepuck Cafe.  I bought it,
took it home, and found the following:

  1. Disk-based copy protection (bleah!)
  2. No multitasking (bleah again!)
  3. Runs very erratically on a 68020 (triple bleah!)

When played in 68020 mode on my 2500/20, the game is *somewhat* playable,
but the sound and music are completely out of sync.  For example, when
the opponent 'snarls' at you, there is usually the sound of glass
breaking, or (more commonly) random noise.  The game seems somewhat
'too easy' in 68020 mode as well.  Note that it does play perfectly
in 68000 mode.

I find this ridiculous in the extreme.  Just to play this (incredibly
addictive) game, I must reboot, hold down both steenking mouse buttons,
select 68000 mode, THEN play the game, and reboot yet another time to get
back to 'real' work.  Why should this be necessary?  I would be perfectly
happy to have the game disable multitasking while playing, so long as it
reenabled it during pauses, and when finished.  This would IN NO WAY impact
the user on a single floppy A500, but would definitely increase the sales
of an otherwise great product.

To the developer's 'credit', the game does allow me to use the original as
a 'key disk' (though this is not documented anywhere).  I was able to
copy the disk, and when booting, the program completely loads before
checking for the protection, at which time you are asked to place the
original disk in df0:.  I can then pop out the copy, pop in the original,
then PRESS A BLOODY KEY, then pop OUT the original again, and pop back IN
the copy (there are data files used periodically in the game).  Some fun, eh?

The big problem with these assumptions is that the basis for the assumption
changes too rapidly.  The 'assumption' that a 68000 based machine is the
'lowest common denominator' is no longer true.  Yet there are still MANY
games that will run on nothing else.  While it may (for the time being)
be true that 68000's make up the majority, it does not imply that all
Amigas are 68000 equipped.

-- 
Chris (Insert phrase here) Seaman |  /o  -- -- --
cseaman@sequent <or>              |||    -- -- -     I'm Outta Here, Man!
...!uunet!sequent!cseaman         |vvvv/  -- -- -
The Home of the Killer Smiley     |___/  -- -- --