Orbit is a freeware space combat simulator in the tradition of Elite, Wing Commander etc, originally written by Steve Belczyk for Win32/Linux systems. Here you can find the port for Amiga/68k by Thomas Aglassinger, which is derived from the Amige/PPC port by Oliver Gantert. For more information, visit the Official Orbit Homepage.
First, you need quite some hardware:
Next, you need a huge pile of libraries, drivers and utilities (unless you have them already). Fortunately, all of them are available for free:
Uff! That should do it.
You need two archives, which are both available from Aminet:
Currently, the installation is not very Amiga-like. Maybe in a later version. For now:
Orbit_*.lhaarchives wherever you like. They expand to a directory named "Orbit", so you don't have to create one manually.
*.libraryends up in
libs:. If you just want to run Orbit, don't bother too much about the environment variables. For more details, see the section on "Tuning Performance" below.
libs:and remove the
040in the name.
ixemul.library. This can also be a pain, but concerning Orbit, just make sure that the appropriate file ends up in
libs:. Take care that it's optimized for your CPU if you're concerned about performance. If you're not concerned about performance yet, believe me, you will be after you ran Orbit the first time. Remember, we're talking about 68k here.
Finally, the interesting part (again, not very Amiga like):
cdto the Orbit directory.
stack 60000. (I watched StackMon while running Orbit, and it announced a maximum of about 50K, so this should be on the save side.)
orbit.exe. But this will not give you much performance. Read on...
StormMesa offers a lot of options to finetune the OpenGL/Glut applications. Orbit is a Glut application, so you can use all the standard Glut options in the command line.
For users of Z2 graphic cards and AGA, these are the most interesting ones:
-forcefsmakes Orbit run on an own screen. Choose a small one, then it's faster. If you have a Z2 graphics card, it makes sense to use 320x240 because the Z2 bus becomes very slow with higher resolutions. If you have AGA, you need the NewWP8 patch from Aminet.
-fastgenerally trades quality against speed
-vfasttrades quality against speed event more violently
-forcedbuses double buffering
On my trusty Amiga 2000 with a 68060/50, Picasso-II and CyberGfx v3, the following seems to work best:
stack 60000 set MESA/FORCE_IR orbit.exe -vfast -forcefs -forcedb
In the screenmode requester select something like 320x240x16, so you won't need any dithering. I've provided some screenshots, so you know what to expect from the above configuration.
Refer to the StormMesa manual for more options and details.