Sad to say, I'm not replying to my own question about Air Combat
Maneuvers under Debian 1.2.4. And I'm not forwarding it again unless
required, and possibly by private e-mail, being that a rather big message.
I just have to point out a couple of things.
1) Ian Murdock is not the maintainer of the package anymore.
On Fri, 25 Apr 1997, Ian Murdock wrote:
> > I had previously sent this to Ian Murdock, who maintains the
> > package (and who invited me to post the question to the list):
>
> Actually, I don't maintain the package anymore; that's why I pointed
> you to debian-user. :)
I'm so sorry, excuse me, of course I couldn't know!
2) I'll add the minimum quick-start hints to give anybody willing to
dig into the problem but NOT using a well running ACM before the chance
to distinguish what VEEERY SLOW means:
- Pentium 90 running both the acms server and the acm graphics frontend.
- 320x200 window (not everything is readable but it's rather fast
even at low altitude maneuvers over the airport; inside a larger desktop
run acm -geometry 320x200, otherwise write a simple script, say ~/goacm,
which you run from text console and which puts in action a XF86Config
file - see attachment - limiting the X desktop to that low resolution,
then calls starx, then reputs "in action" the all-modes XF86Config; a
similar limit to 1024x768 could work e.g. for "Battle Zone").
- Mouse cursor centered in the head-up display.
- Press "h" twice: flaps down.
With a slower machine eventually press "r" twice: radar off.
- Immediately one after the other press "4" and "a": full throttle and
afterburner.
In a well running ACM:
........................................................................
>>> IN 3-4 SECONDS the left vertical rudder should reach 150 (knots) <<<
........................................................................
- Here if you find it interesting you can smoothly pull back the mouse
and take off, keep the small circle (flight path marker) on the 20
degrees up line, at 200-250 knots press "y" twice (flaps up), at 400-450
knots press "a" (toggle afterburner to off)... you'll enter the
clouds and exit soon, press "n" and shake the mouse a little, then
press "n" again... you have better read the postscript documents if you
really decide to "fly" ACM, and train quite a lot to land safe (if
you're not a pilot, I mean), which is to me the most beautiful thins,
especially with a broken engine or unbalanced plane or at least with
minimum throttle (20%, which is anyway less difficult than with broken
engine or with no fuel).
BY THE WAY, the "rotor" mode of xlock seems very slow too, isn't it?
I mean, under an old Slackware '95 (and 3.1 December 9.6 and other
distributions I gave a look at) I saw it so fast that full geometric
shapes appeared quickly changing, and not a running point.
I find Debian great under many aspects, pon/poff, mgetty, I've well
understood and configured the /etc/X11/fvwm2/.fvwm2 hooks and noticed that
the install-deinstall procedures for some packages automatically update
the /etc/X11/fvwm2/menudefs.hook (I'm thinking about posting a couple of
messages after this, one to help ex-Slackware users with a minimum fvwm2
menu setup and one for the Italian users to fix correspondence of a few
keys).
I was really hoping to be able to rebuild not only ACM version 4.7
but also that (still beta?) 4.8 with that IEEE standard for networked
distributed computation...
I find fast X graphics fascinating since I was a kid (what a surprise
it was to have Battle Zone, cbzone, under my first Linux install). Nothing
you can find under Windogs... as A LOT of other goodies anyway.
Nicola Bernardelli <[EMAIL PROTECTED]>
---------------------------------------------------------------------------
Please use <[EMAIL PROTECTED]> for messages from any kind of
robot, such as mailing lists. From that address no autoresponse
messages will return even when I'm not at home.
---------------------------------------------------------------------------
# The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64)
Section "Screen"
Driver "accel"
Device "California Graphics ST2000p"
Monitor "Sony Multiscan 17se"
Subsection "Display"
Depth 8
Modes "320x200"
# Modes "1024x768" "1280x1024" "1504x1128" "1600x1200"
"1600x1280" "320x200" "400x300" "640x480" "800x600"
ViewPort 0 0
#Virtual 1024 768
#Virtual 1280 1024
#Virtual 1600 1280
EndSubsection
Subsection "Display"
Depth 16
Modes "320x200"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "320x200"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "320x200"
ViewPort 0 0
EndSubsection
EndSection
