******************************************************************************

                       Powerslide patch,  version 1.04
                     Copyright + 1998-1999 Ratbag Pty Ltd

                            www.ratbaggames.com

******************************************************************************

This is a patch for Powerslide, which can be used to create Powerslide version
1.04 from versions 1.01, 1.02 or 1.03.

The previously released patch was version 1.01 - versions 1.02 and 1.03 were
not made available as patches.

As of this version, there is no longer any distinction between the 
US/Australian and European versions of Powerslide. This patch can be applied
to either installation.

Note that if you have version 1.00 (the original release version), you must
first apply the version 1.01 patch, before applying this patch. You must use
the version of the 1.01 patch which is appropriate to the version of
Powerslide you have (eg US/Australian or European). If you don't know which
version 1.01 patch to apply, use the European one.


1. Added features
2. Bugs fixed
3. Command line options

******************************************************************************
   1. Added features (since v1.01)
******************************************************************************

- Added the ability to perform GameGauge speed-profiling tests, via a
  command-line option.
- Support for higher resolution modes on the Banshee and Voodoo3 graphics
  cards.

******************************************************************************
   2. Bugs fixed (since v1.01)
******************************************************************************

- Voodoo3 cards are now detected as a Glide card, not a Banshee. This means
  that specular will work on a Voodoo3.
- Problem with HRESULT errors on certain sound cards.
- Problems with European copy protection not recognising certain types of
  CD drives.
- Problems with the European copy protection crashing on some machines.
- A command-line option to fix slow mouse movement on certain video cards.

******************************************************************************
   3. Command line options
******************************************************************************

This version includes a large number of new command line options. Most of
these new options are used to perform GameGauge tests, or to set graphics
options from the command line so that GameGauge scripts can be written.

Command line options can be entered on the command line, or placed into the
ps_clo.txt file in the Powerslide installation directory. A utility 
(ps_clo.exe) is provided to make it simple to edit this text file. A shortcut
to this utility is in the Start Menu under the Powerslide group.

The full list of Powerslide command-line options is:

******************************************************************************

GAMEGAUGE OPTIONS

-ggfps

This makes Powerslide do a GameGauge fixed demo loop, of the dam track.
Powerslide will jump straight to the demo when run, execute the demo, output 
the results file, and then quit. You can press a key or mouse button during
the execution of the demo to quit it early; the results file is still
written for the amount of demo played.

This (ie the dam track) is what we recommend is used for the GameGauge tests.
However, if you wish to try a different track for comparison, the command 
line option is:

-ggfpst <track name>

Where <track name> is the name of the track to perform the demo on. This can 
be one of:

speedway
sandblaster
urban
dam
mineshafted

The approximate lengths of the demos (in seconds) are:

speedway       58
sandblaster    71
urban          95
dam            48
mineshafted   105

Note that while you do need the Powerslide CD to be in the drive to actually
run a race, you *DON'T* need the CD in order to run the profiling demo 
test. If the CD is present while running the profiling demo, then the CD music
will be played, which might effect the frame rate.

The GameGauge results file is called fps.txt, and is placed into the 
Powerslide installation directory. The format of this file is something like:

67.63 Powerslide v1.03
45 Min
100 Max
46 Second 1
...

The 67.63 is the average frame rate of the demo. The 45 and 100 on the Min and
Max lines specify the minimum and maximum frame rates respectively. Finally,
the '46 Second 1' line is repeated a number of times, showing the frame rate
every second as the demo runs. These numbers are all calculated using the
method which GameGauge requires.

******************************************************************************

GRAPHICS OPTIONS

-forced3d

As explained in the original readme file, forces Powerslide to use Direct3D,
even if a Glide card is installed.

-forceglide2

Also as explained in the original readme file, forces Powerslide to use the
generic Glide graphics driver, even if a Banshee is detected. If a Banshee is
detected, a different texture management system is used. At the time of this
build, the latest available Banshee drivers still do not support multibase
texturing, and so use of the -forceglide2 switch if you have a Banshee still
produces a corrupted display.

-res <x res>x<y res>

(eg -res 640x480, or -res 1600x1200)

This sets the resolution for rendering. Powerslide supports any resolution
that the video card can support. If the resolution specified on the command
line is not supported, the resolution is either set to a 'close' one, or is
unchanged from the previous setting.

-bpp <bpp>

Sets the desired bits-per-pixel for rendering. 16 or 32 are the usual 
choices. If you use -bpp without also using -res, the resolution will be set
to 640x480 (at the desired bpp, if available). If you use -res without using
-bpp, it will be set to 16bit (if available).

-shadows <val>

Specifies whether to render shadows. <val> should be 1 to render shadows, or
0 to not render shadows.

-particles <val>

Specifies whether to render particles. <val> = 1 to render particles, 0 to
not.

-trilinear <val>

Specifies whether or not to do trilinear filtering, on a Direct3D card. Under
Glide, if trilinear is supported (ie a Voodoo 2 or 3 is being used), then
trilinear filtering will be used automatically. <val> = 1 to do trilinear
filtering, 0 to not.

-specular <val>

Specifies whether or not to put specular highlights on the cars. This is only
supported on the Voodoo 2 and 3. <val> = 1 to do specular highlights, 0 to not.

-allow_d3d_3dfx

Allows the use of secondary 3DFX video cards under Direct3D. This is most 
useful for comparing a 3DFX video card with a non-3DFX card in a GameGauge 
test. By running both cards under Direct3D, the tests both run the same
Powerslide code, meaning that any speed differences are a result of the
graphics card alone.

-d3ddevice <val>

Specifies which device out of those enumerated by Direct3D to use. If <val>
is 0, the primary device is used, if it is 1, the secondary, and so on if
other devices exist in your configuration. If this command-line option is
not used, and -ggfps *is* used, then the demo will always default to the
primary display device (if running under Direct3D).

-autodetect

Forces Powerslide to re-autodetect the optimal graphics driver based on your
hardware configuration.

-glide2vsync

Forces the Glide 2.x graphics driver to wait for the vertical refresh.

-d3dflip

If using Direct3D, forces the code to wait for the card's vertical retrace. 
May remedy problems with certain cards.

-d3d_3buf <val>

Sets whether the Direct3D graphics driver should perform triple buffering.
<val> should be 1 to perform triple buffering, 0 to not.

-ddemulation

Uses DirectDraw emulation for the game interface, which fixes the problem
with slow mouse movement on certain video cards.

******************************************************************************

SOUND OPTIONS

-nopollsound

Due to incompatibilities between the beta and release drivers for the EAX 
sound card, the notification-driven sound system used in Powerslide 1.00 does 
not work with EAX sound cards (with release drivers). Therefore as of v1.01 a 
less efficient polling sound system is used. The -nopollsound option can be 
used to re-enable the more efficient notification-driven sound system, but 
will cause problems if you have an EAX sound card.

-eaxfactor <num>

Can be used to change the level of reverb if you have an EAX sound card. The 
reverb levels are multiplied by <num>, recommended values are between 0.5 
and 3.0.

******************************************************************************

MISCELLANEOUS OPTIONS

-fflevel <num>

Can be used to increase the amount of force-feedback delivered if you have a 
force-feedback device. <num> is an integer in the range 0 to 10; 0 means the 
default level of force, and 10 means 3.5 times the force.

******************************************************************************
Powerslide + 1998 Ratbag Pty Ltd. All Rights Reserved. Published and 
Distributed by GT Interactive Software Corp. GT and the GT Games Logo are
trademarks and the GT Logo is a registered trademark of GT Interactive
Software Corp. Powerslide, Ratbag, the Ratbag logo, and the Difference Engine 
are trademarks.
