Debugging Your Game

     Debugging in FreeVector can be a difficult task or it can be an easy one. It depends on the error. If FreeVector cleanly shuts down during the process of running a game. Then the first place to look is in the errors.log file located in the FreeVector root directory. This may state that it could not load a file or a data set. If it tells you that it could not delete a level, then a resource such as a script or an FX file is causing a critical error. These are the most difficult to find and is usually corrected by backtracking ones work.

     Here are a few tips to avoid errors from cropping up while building a game with FreeVector.

• Be sure that there are no extra spaces between values in data files.
• Be sure that animated models have all their bones attached to at least one vertex.
• Only access script local variables in the Init order of any script.
• Make sure your textures are a power of two.
• Be certain that your FX files compile properly.

     Sources of errors that may not cause the engine to shut cleanly include:

• Errors in the menu or game script.
• Error in the FX files.
• Some missing media.
• Errors in the level file.
• Misplaced curly brackets in a script.