Game Killer/Game_Killer.bin/796.DEMITOR.KEY

Text File | 1990-02-11 | 8KB | 265 lines

 "s(1)", 31, -1
 "s(2)", 31, 31, -1
 "s(3)", 31, 31, 31, -1

 "view(front)", 70, 72, -1
 "view(front,right)", 70, 73, -1
 "view(front,left)", 70, 71, -1
 "view(right,front)", 70, 73, -1
 "view(left,front)", 70, 71, -1
 "view(right)", 70, 77, -1
 "view(left)", 70, 75, -1
 "view(rear,right)", 70, 81, -1
 "view(rear,left)", 70, 79, -1
 "view(right,rear)", 70, 81, -1
 "view(left,rear)", 70, 79, -1
 "view(back,right)", 70, 81, -1
 "view(back,left)", 70, 79, -1
 "view(right,back)", 70, 81, -1
 "view(left,back)", 70, 79, -1
 "view(rear)", 70, 80, -1
 "view(back)", 70, 80, -1
 "view(down)", 70, 76, -1

 "zoom(in)", 13, -1
 "zoom(out)", 12, -1
 "zoom(+)", 13, -1
 "zoom(-)", 12, -1
 "zoom(++)", 13, 13, -1
 "zoom(--)", 12, 12, -1
 "zoom(+++)", 13, 13, 13, -1
 "zoom(---)",  12, 12, 12, -1
 "zoom()", 14, -1
 "zoom(reset)", 14, -1

 "lights", 38, -1
 "strobe", 24, -1
 "menu", 1, -1
 "sound", 16, -1
 "gear", 34, -1
 "nav/dme", 48, -1
 "carb", 35, -1

 "map(on)", 69, -1
 "map(off)", 69, 69, -1
 "window(1,on)", 26, -1
 "window(1,off)", 26, 26, -1
 "window(2,on)", 27, -1
 "window(2,off)", 27, 27, -1

 "clouds", 4, 32, 2, 57, -1
 "storm(on)", 4, 48, 10 , 11, 6, 11, 11, 11, 11, 28
              30, 11, 2, 6, 11, 11, 11, 28, 57, -1
 "storm(off)",  4, 48, 10, 11, 11, 11, 11, 11, 11, 28
              30, 11, 11, 11, 11, 11, 11, 28, 57, -1

 "spot", 31, 31, 31, 70, 80, 14, 12, -1

 "end_of_data", -1


 DEMITOR.KEY revision 0.0 MACRO COMMAND DICTIONARY
 -------------------------------------------------

 Format and syntax, this file:
 --    All macros end in -1 with at least one intervening key
 --    End_of_data statement ends in -1 with no intervening keys
 --    All macros in this file must be surrounded by quotes

 Format and syntax, macro usage:
 --  When  macros  are  entered  directly  via  DEMITOR's   (E)dit
 (C)omment  function the macro command must *not* be surrounded by
 quotes.
 --    When macro commands are used in a storyboard file they  must
 be surrounded by quotes.

 "s() macros toggle through cockpit, tower, track and spot",-2

 External Macro notes
 --------------------
 External macros are the ones found in this file.

 Note the duplicate labels to allow easier use;

 e.g.- view(back) = view(rear)

 "spot"  illustrates  a  custom macro which does several things in
 one frame:  toggles  "S"  three  times  (changing  to  spot  from
 cockpit),  puts  the  spot  plane behind yours,  resets zoom then
 zooms out once for a fuller view.


 Internal Macro Command summary
 ------------------------------
 Internal macros are 'built in' to DEMITOR.EXE

 cut() macros specify the portion of the demo  that  you  wish  to
 save. This is obviously helpful when you want to get rid of those
 extra last few frames that aren't contributing (but recorded just
 in  case).  Less  obvious is its use in generating partial copies
 for review (e.g.- looking at the last third of a long demo to see
 if you got the timing the way you want,  without having  to  wade
 through  the  first  two thirds).  Using cut() in this way during
 demo development can be a life (or marriage) saver ("Oh, no,  not
 again!").

 "cut(from)"          starts save from this frame
 "cut(to)"            ends save at this frame


 panel() macros allow switching from a standard cockpit/instrument
 panel  configuration  to  one where the panel has been moved down
 off the screen and the cockpit view has been  expanded  to  cover
 the entire screen. Since the position of the panel determines the
 vertical position of the message bar,  *even if* you're in a view
 mode other than cockpit,  panel() commands may be used  to  shift
 the message bar up and down.  As the full-screen spot view always
 places your aircraft in the middle of the screen,  with the stan-
 dard  panel configuration,  your messages will hide the aircraft;
 this is a perfect time to use  panel(down)-  your  messages  will
 show up at the bottom of the screen and the aircraft will be seen
 just fine.

 Experiment with this to get the feel of it. The panel macro's ac-
 tually splice in a mode file to the demo (panel macros won't work
 if no leading mode is attached) and therefore add about 500 bytes
 per use to the demo file,  therefore,  use sparingly if your demo
 is a large one.

 Panel functions carry a number  of  current  settings  over  with
 them: Throttle setting, time (takes into account both 1 sec and 5
 sec intervals),  sound on/off,  gear up/dn, lights on/off, flaps,
 and view mode (cockpit, spot,  etc).  Others parameters will take
 the values as set in the leading mode.

 "panel(off)"         injects corrected mode file with the panel
                     moved to the bottom of the screen and a
                     full-screen cockpit view (useful for full-
                     screen views with comments at the *bottom*
 "panel(down)"        same as "panel(off)"
 "panel(on)"          normal panel and cockpit view
 "panel(up"           same as "panel(on)"


 The  turb() macros are for those who enjoy some realistic texture
 in their demos but find the actual FS4 turbulence options too ex-
 treme (a common complaint).

 "turb(on)"           initiates medium turbulence
 "turb(high)"         initiates heavy turbulence
 "turb(low)"          initiates light turbulence
 "turb(off)"          ends turbulence


 The spin() macros are simply just for fun;  try it somewhere  be-
 tween touchdown and full-stop.

 "spin(left)"         initiates spin to left and drops wing
 "spin(right)"
 "spin(off)"          completes spin


 The  roll()  macros are to introduce the joys of vertigo to those
 of us who are not yet adept at aerobatic flying.  Perhaps it will
 be an inspiration to learn.

 "roll(left)"         initiates roll to left
 "roll(right)"
 "roll(off)"          completes roll




 Instructions
 ------------
 The  DEMITOR  command  processor is case and space sensitive.  It
 acts only on exact matches.   So keep a  printout  of  this  file
 handy when editing or preparing your storyboard files (*.BRD).

 You  can  add your own custom macros to the DEMITOR.KEY file.  To
 learn which key numbers (scan codes) to use,  you may make a demo
 incorporating only the actual keypresses of interest and then use
 DEMITOR  to  view the corresponding key numbers at the Frame Edit
 menu.

 Adding to this file is simple: INSERT the new command and key se-
 quence before the "end_of_data" entry, following the syntax:

 "[macro name]",key 1,key 2,...,last key,-1

 Always test new macros: most will work perfectly as intended  but
 some  (involving  menus) may require special diddling to get them
 to function (e.g.- padding menu data entry with leading zeros) or
 restrictions on usage (ensuring that subsequent  few  frames  are
 free of keypresses).

 There is a detector built into DEMITOR that will indicate whether
 a demo has used the artificial effects like roll,  spin, and tur-
 bulence.  Instructions for use are only $299 per copy- we pay the
 postage (if you can't afford this just  look  at  the  statistics
 display after loading a demo; a plus in the parentheses means the
 demo includes artificial effects).

 DEMITOR is a shareware product;  if you find it a useful addition
 to your FS enjoyment, please send the $10 DEMITOR license fee to:

           Kyrna Wheeler
           KikiWare
           17 Ferguson Road
           Warren, NJ
           07060   USA

 Please include your return address or CIS # and specify the  ver-
 sion you are licensing. Thank you,
                                    Laemming Wheeler
                                    DEMITOR author/Kyrna's dad
                                    CIS 71317,2616

                                ***