Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!darkstar!ucscb.UCSC.EDU!davids From: davids@ucscb.UCSC.EDU (Dave Schreiber) Newsgroups: comp.sys.amiga Subject: Re: Game vs Multitasking Keywords: Game Users Message-ID: <3916@darkstar.ucsc.edu> Date: 30 May 90 17:03:44 GMT References: <3871@darkstar.ucsc.edu> <9143@rouge.usl.edu> Sender: usenet@darkstar.ucsc.edu Distribution: comp Organization: UCSC Open Access Lines: 57 In article <9143@rouge.usl.edu> wakres01@pa.usl.edu (1712 Stelly John B) writes: >In article <3871@darkstar.ucsc.edu> davids@ucscb.UCSC.EDU (Dave Schreiber) writes: >> >>In article mt87692@tut.fi (Mikko Tsokkinen) writes: >>> And BTW my game contains fractal landscape and complex 3D objects, you >>>seriously think 68000 can run it and some other programs simultaneusly? >>>NO WAY MAN! >> >>Of course a 68000 can run it and other programs. It's not like the >>chip is going to explode or something if you try it :-). Your game will >>just run more slowly that it otherwise would (depending on how many tasks >>are being run, how processor intensive they are, their priorities, etc.). >>The choice, however, should be left up to the user; I personally don't >>like being told what my system's capabilities are when the programmer has >>no idea just what my system is. > >Oh, come on, you know what he means... the game would be unplayable on a 68000, What if I don't have a 68000? Or what if I don't mind? When I'm playing the game, _I_ want to decide for myself. >unless it devotes its full attention to the game. But again, if you intend to >sell your game to ANYONE other than most people who use their amiga primarily >for games, you must make your program multi-task, that is a sacrafice most will >be unwilling to make. > Exactly. If the game is very CPU intensive I will make sure not to run any other programsalong with it (or set priorities properly). However, I don't like being told that: 1) My machine can't handle running the game without disabling multitasking (or even that I will find the game unplayable while running something else) when the programmer doesn't know what system I using. 2) I can't be TRUSTED to not to set up my environment properly so the game won't be affected (for the novice user who doesn't know how, why not just make the game bootable, with a startup-sequence that insures that the game is the only thing being run; let the rest of us run it from wherever we usually run programs). Question: is there a signifigant difference between how fast a program will running in a monotasking environment, as opposed to one where simply no other user tasks are being run? Hmmm, I'll have to check that the next time I'm at my machine... > >John B Stelly III -- Dave Schreiber The blue leprechaun at davids@slugmail.ucsc.edu (prefered but flakey) or (not both) davids@ucscb.ucsc.edu "Coffee, Darling?"