GP1Track V1.01
==============

Description
-----------

GP1Track is a simple program which analyzes track files from F1GP/WC and outputs a text file detailing the known (and in some cases, unknown) data contained in the file.

Please keep in mind that this is not totally user-friendly, the output file is a large text file (100-150k approx.) with all the information in it. In many respects this makes it difficult to find things quickly, but the aim of this program is to help with the exploration of trackfile formats - not as a tool for creating/editing tracks.


Usage
------

The program can be run from any directory, although it's easiest to run it from the same directory as the trackfile you wish to analyze. General usage is as follows:

   GP1Track.exe <trackfile> [output] [-y]

   Required parameters:
     * <trackfile>  - Specifies the trackfile to analyze. It is assumed that the filename given is a valid F1GP/WC trackfile.

   Optional parameters:
     * [output]  - Tells the program what name to use for the output file. The default name is "track.txt". A .txt extension is recommended for ease of viewing.
     * [-y]      - Automatically overwrite the output file if it already exists. This is handy for batch files when analyzing more than one trackfile at a time.

The trackfile to be modified MUST be the first parameter given; optional parameters may be given in any order.

Example usage:

   c:\> gp1track f1ct01.dat track01.txt

   Analyzes f1ct01.dat, outputting the information to track01.txt. If this file already exists, the user will be asked whether to overwrite the file or not (if not, the program aborts).


Support
-------

   Any questions, suggestions, theories on unknown data should be sent to:

   lazwatson@yahoo.com


Contributions
-------------

   Of all the information contained in the output of this program, very little of it was 'discovered' by me. Some of the information in the trackfiles is identical to that in GP2 files, or was outlined by people in the GP2 community.
   The majority of the codes and file structures are similar, but not identical, to GP2 files, and were located in F1GP/WC files by comparing the values in the trackfiles to the data that was most likely going to be present, based on GP2-trackfile specifications and the differences between the two games.
   Most of this information is therefore only available thanks to the excellent work done by many, many contributors in the GP2 community.


Version History
---------------

V 0.90  29th September 2000

      - Analyzes trackfile header, track data, CC-line data, and Pitlane data.
      - No error checking whatsoever except for when stepping through track and pitlane data, where unknown commands are reported.
      - Static output file name, no way to change it.
      - All commands used by the default F1GP/WC tracks are recognised, but only one (track segment) has a description.

V 1.00  30th April 2001

    Up to this point gp1track has just been for my personal use, but after consultation with Barrie Millar it has been decided that this version will be released - with an update coming soon.

      - Some slight changes made to the output text by Barrie.

V 1.01  9th May 2001

      - Reworked some code to neaten command definitions, allowing easier addition of known commands and making memory use more efficient.
      - Added known object information: object definition list, internal object structure headers.
      - Updated the command and argument descriptions, based mainly on equivalent GP2 information.
      - Added some more error checking and command line options, to improve ease-of-use.
      - The last sections of the file are now included in the output.
      - More efficient build options saving 20kB in size.


Disclaimer
----------

The usual thing... I make no guarantees regarding the reliability or safety of this program, I cannot be held responsible for any problems arising directly or indirectly from the execution of this program.

I can, however, guarantee that this program is designed to do exactly what it says, and contains no deliberately-malicious code.

(May I add, long-term software or hardware problems caused by the use of this program are EXTREMELY unlikely - otherwise I wouldn't use it myself... :))


========================================================
Program and documentation by Larry Watson (9th May 2001)