home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!chaph.usc.edu!aludra.usc.edu!not-for-mail
- From: cokin@aludra.usc.edu (Darren Cokin)
- Newsgroups: comp.sys.mac.games
- Subject: Re: Falcon MC Demo (at la
- Date: 22 Nov 1992 14:58:55 -0800
- Organization: University of Southern California, Los Angeles, CA
- Lines: 21
- Distribution: world
- Message-ID: <1ep3bfINNr1l@aludra.usc.edu>
- References: <1873.339.uupcb@pcb.batpad.lgb.ca.us>
- NNTP-Posting-Host: aludra.usc.edu
-
- In article <1873.339.uupcb@pcb.batpad.lgb.ca.us> glen.kawano@pcb.batpad.lgb.ca.us (Glen Kawano) writes:
- >
- >Someone was complaining in another message that the MouseStick didn't
- >work right; to use the MouseStick, make a set with vector speed set at
- >70. Set null zone at 30 or so. Tracking unchanged. Direct zone and
- >direct output should be zero. Set the buttons any way you want (I have 1
- >and 3 for throttle, 2 as trigger). Of course, set the game to MouseStick
- >control. With these settings, Falcon's response is extremely good, in
- >the same league as Flight Simulator 4. (Actually, I don't know what the
- >roll rate of the F-16 is, but it seems kind of slow in this game.)
-
- That was me. Thanks a lot, this works great. Why didn't they just say
- to use vector control? The game now works great with my stick, and is much
- better than the mouse (I can't stand the keyboard). I'm upset with the entire
- lack of documentation that came with the demo. They didn't mention this, or
- what any of the readouts mean. I've never really played the original game,
- nor have I been in an F16, so I have no idea what anything in that heads up
- display means.
-
-
- Darren
-