Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!sdrc!evtracy From: evtracy@sdrc.UUCP (Tracy Schuhwerk) Newsgroups: comp.sys.amiga Subject: Re: StarFlight..Oh damn! Summary: Starflight Speed... Keywords: Ya got a lifetime? Message-ID: <1066@sdrc.UUCP> Date: 22 Jan 90 13:42:43 GMT References: <1990Jan20.051542.12167@dvinci.usask.ca> Organization: SDRC, Cincinnati Lines: 46 In article <1990Jan20.051542.12167@dvinci.usask.ca>, jim@skatter.uucp (Jim Bergstrom) writes: > > I have a major problem with this game. I don't have a lifetime to play > it....and believe me, it will take you a life time to play the bloody thing! > > Now, this game has major entertainment value, but unfortunately, it > takes to ruddy long to play. I'm talking time here, playing time! Now I have > been driven to the point of absolute frustration and have clocked this game with > a stopwatch. First thing though: I am attempting to participate in this game > with an Amiga 1000 with 2 meg and have tried both 1.2, 1.3 kickstart plus two > copied disks, (this game allows you to copy it and use a code wheel), and have > gotten no where. Now back to stopwatch, this is what I have clocked, beleive it > or not: > It takes approximately 8 minutes for the computer to catch up with you > every time you move the mouse to an action sequence, ie.. click mouse for > mineral pickup, wait 8 minutes. Click mouse for scanner, wait 8 minutes. > Click mouse for map, wait 8 minutes. Now, I'm being relatively modest with thes > times, in some situations I have waited up to 17 minutes for something to > happen. This is a bloody shame! I can see " ELITE " blown out of the water > with this game, but unfortunately, I don't think I'll live long enough. I have StarFlight and run it on my Amiga 1000 with 512K (AUGH! I NEED MORE MEMORY!) using KS 1.3 and have had no problems. The only difference in the 2 systems that I can see from your description is the extra 1.5 meg of RAM. I was blown away by the times you gave (defective stop watch???) because I can't think of anything I have that sits for 8 minutes (except maybe some of the rendering software I have...) and 17 minutes is really long! I wonder if the extra memory is causeing some sort of major hangup. I agree with you on the game (I'm not concerned as much with awe inspiring graphics on a game of this type... just interesting exploration) it is really a good game! I haven't used a stop watch to check out times, but I would guess that the slowest thing I have seen about the game is an open port landing sequence (which I only take every once in a while... if I need a break to get a drink or something). Good luck solving the problem, I would check out the memory situation (maybe a "chipramfirst" type of command in the startup?) Tracy (uunet!sdrc!evtracy) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /// _______________ / / / /// /// / (___ _ /_ /_ _ __ /_/ /// \\\/// / . _____)__(__/ /__/_/_/ /__/_/_/__(/__/ (__/ \ \\\/// \XX/ Structural Dynamics Research Corporation \XX/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=