********************************** 
* How to use the TIMING.SYS-File *
********************************** 


The usual way
-------------
One of the most astonishing features of the game "Crown of Creation 3D" is its 
compatibility to all kinds of Falcon 030. In general, Falcon games are (if 
there are any at all) coded only for the standard Falcon with 16MHz CPU-tact, 
32MHz DSP-tact and simple bus-handling. And if there should exist a game to be 
run on extended Falcons, they simply brake them down to ordinary Falcons so 
that their speed isn't andequate.


The new way
-----------
"Crown of Creation 3D" goes a different way of best compatibility that should 
allow to run it on nearly all Falcon platforms. Therefore, separate timing-
algorithms were developed to adjust the program to all possible speed 
configurations. For most Falcon extensions, this integrated service will allow 
highest stability with best speed and the player won't have to care about it at 
all. And if the system occasionally gets unstable, the game will inform you 
about it and automatically correct the problem for a smooth continuation of the 
game. So, if you belong to the lucky Falcon-users with stable hardware 
configurations, and have no (or only seldom) problems with the game, you 
actually needn't go on reading.
But there might be some exotic Falcon-configurations that make quite impossible 
to foresee all timing situations. As all Falcon owners should be able to run 
the game on their computers, an additional solution was implemented. Therefore, 
the player's cooperation is needed, because by manipulating the TIMING.SYS-
file, he can configure the timing-relations of the game just as it's necessary 
for his system.
The success of this new way has already been tested on several widespread 
Falcon-systems:
 -naturally conventional Falcon 030 without any extension
 -pure CPU-speeder both 32 and 40MHz
 -DSP-Versions with 32 and 50MHz
 -FX-Card and Speed Resolution Card in each case with sensational frame rates


Indications for problems
------------------------
So how do you recognize, if the game isn't stable on your own system? The 3D-
engine itself gives first hints by informing the player that an error occurred. 
If this happens frequently or real system crashes occur, it's very likely that 
you are mistreated by timing-problems (esp. communication problems between CPU 
and DSP). So don't unnecessarily insult any Rebelsoft-member, but try to solve 
the problems by adjusting the TIMING.SYS-file. The player's first task is to 
find out, which program part among the following ones is responsible for the 
problems:

-the music routine: Most certainly this part is to blame if errors occur while 
 playing a MOD-file (a music piece), for example in the intro- or extro-
 sequence, in the weapon hangar and on other occasions.
-the stars routine: Here errors can only occur during flight. Most certainly 
 this part is responsible if neither a 3D-object is displayed nor a sound can 
 be heard. If errors happen only with 3D-objects and/or sounds, the stars 
 routine becomes rather improbable.
-the object routine: If errors occur especially when objects are displayed, 
 this part should be examined. This case gets more probable the more and 
 greater objects may be seen. Object errors may occur in the main menu and the 
 missions screen, too.
-the sound routine: It's responsible for all kind of sound samples that don't 
 belong to a music piece. So, if errors occur for example when shooting your 
 laser gun, check this out. But similar sound effects may be used outside the 
 actual 3D-engine, too.


The solution for the problems
-----------------------------
If you succeeded in finding out the unstable program part, you immediately can 
start solving the problem. Therefore you must load the TIMING.SYS-file into any 
ordinary text editor. Then you'll recognize that there are two categories of 
parameters in it: the _SYS-part and the _USER-part. The _SYS-part shows the 
timing-data found out by the internal timing-routines, whereas the _USER-part 
can be written by the player by proper values to override the (hopefully not) 
critical internal values.
After installing the game, the _USER-part's variables are all filled with -1. 
That means, that the user-timing is out of order and everything depends on the 
internal routines. So, if one (or some) of the internal routines don't provide 
enough stability, you have to write your own (better) values to the 
corresponding _USER-part variable. Generally you can say that the higher the 
value, the more stable (and slower) the system runs. To find out which routine is 
influenced by which variable, read the following lines:

  SND1_: sound routine for one channel; if you guess that errors occur only 
         when one voice can be heard, adjust the SND1_USER parameter
  SND2_: sound routine for two channels; if errors occur only when two voices 
         simultaneously can be heard, adjust the SND2_USER parameter
  SND3_: sound routine for three channels; if errors occur when three voices 
         simultaneously can be heard, adjust the SND3_USER parameter
  STARS_ and
  STARR_: parts of the stars routine; if errors occur while displaying stars, 
          try out whether STARS_USER or STARR_USER must be incremented to 
          improve stability
  OBJS_ and
  OBJR_: parts of the object routine; if errors occur while displaying 3D-
         objects, try out whether OBJS_USER or OBJR_USER must be incremented to 
         improve stability
  MUSIC_: music routine; adjust the MUSIC_USER parameter to stabilize the music 
          pieces

When manipulating the TIMING.SYS-file, consider the internal _SYS-values as 
lead for your own. Always increase the parameters by 1 not to waste internal 
speed by chosing a too great value. If you write down a value too high for the 
internal timing routines, the program independently limits it to the maximum 
possible value.


The last hope
-------------
Despite our great efforts there might occur circumstances in which you can't 
convince your game to run. That could have other reasons than the program 
itself. For example you might be the proud owner of a high-tech extension card 
with the only disadvantage that its highest speed level isn't stable. In this 
case, our internal timing routines naturally can't adjust the hardware 
weakness. But the solution may be very simple: try shifting down your card to 
the next speed level down and your problems hopefully have disappeared.
    Further problems can occur when certain accessories or auto-folder programs 
are at work. Then better deactivate them all and in the worst case reboot with 
the CTRL-button pressed to really eliminate all possible troublemakers.


Summary how to use the TIMING.SYS-file
--------------------------------------
 -only change TIMING.SYS when the CPU/DSP-Error appears to often
 -recognize which program routine is responsible for your timing problems: 
  sound routine, star routine, object routine or music routine
 -load the TIMING.SYS-file into any text editor
 -adjust the corresponding _USER-parameter with a value greater than the 
  internal _SYS-parameter/ than your own _USER-parameter
 -too great values automatically are limited to their maximum
 -DON'T FORGET: write -1 to a variable, if you want to trust the corresponding _SYS-values of 
  the internal routines
 -restart the game
