BuzzingCars version 1.0 /e DEMO
-------------------------------

BuzzingCars is a completely crazy racing. You must carry out
various missions and races to earn credits so you can buy
new cars. If you find some missions boring or too difficult
you can skip them and replay other missions you like more to
earn enough credits to get on to the next level.


Minimum System requirements
---------------------------

- PC with Windows 95/98/ME/2000/XP
- DirectX8a
- P500 with 64 Mbytes RAM
- 3D accelerator board with 16 Mbytes RAM
- Voodoo boards are not supported

To play the demo, DirectX 8a must be installed on your computer.

If your computer is slow and can't display more the 15 to 20
frames per second (fps) the cars become difficult to control.
In order to increase the frame rate you can click on the
"Options" Button and tune the settings in the "Graphics" tab.


Controls
--------

Driving your car is easy in BuzzingCars, you need only 6 keys:

- UP = accelerate
- DOWN = brake and backwards
- LEFT = turn left
- RIGHT = turn right
- Space = handbreake
- Enter = Horn

You can redefine all controls in the game by pressing the
"Options" button and the the "Controls" tab.


Steering wheel, gamepad and joystick
------------------------------------

BuzzingCars is compatible with steering wheels, gamepads and
joysticks.

Gamepads and joysticks can also be used. By default the buttons
are assigned as follows:

- Button A: handbrake
- Button B: horn
- Button C: change camera view

In the user interface you can use the gamepad/joystick as follows:

- Joystick left/right: highlight previous/next button
- Joystick up/down: change selection in a list
- Button A: press highlighted button
- Button B: cancel


Fine tuning
-----------

In order to allow you to find the best settings for your
computer, you can instruct the computer to display the current
frame-rate. Hit the keys Ctrl+Break, type the command "showstat"
(without the quotes) and validate with the Enter key:

    Ctrl+Break showstat Enter

The frame-rate and some other parameters will then constantly
be displayed on the upper part of the screen, for example:

    32.46 fps T=11558 (640x480x16)

The first number corresponds to the frame-rate (fps = "frames
per second"), i.e. the number of images per second displayed.
The second number indicates the number of triangles displayed in
the scene.
The 3 last numbers in brackets indicate the resolution and the
number of bits per pixel.

All the options are saved in the file buzzingcars.ini. You can
edit this file in any text editor, for example the notepad in
Windows.


Problems
--------

The file buzzingcars.ini can be modified by hand in order to
resolve certain display problems that might occur. Don't add
new lines in this file but only modify existing lines. You
must quit BuzzingCars prior to modifying this file.

If vegetation is poorly displayed or not even displayed at
all try:
	[Setup]
	GadgetQuantity=1.00

If is still doesnt get displayed try:
	[Engine]
	AlphaMode=0
or
	[Engine]
	AlphaMode=2

If a square appears arround the shadows try:
	[Engine]
	WhiteSrcBlend=9
	WhiteDestBlend=6
or
	[Engine]
	WhiteSrcBlend=6
	WhiteDestBlend=3

If this doesn't work you must remove shadows:
	[Engine]
	WhiteSrcBlend=0
	WhiteDestBlend=0
	[Setup]
	GroundShadow=0

When an object gets in the way between the camera and the car, the
object becomes transparent to some extent. If the objets do not get
transparent enough, try this:
	[Engine]
	StateColor=0
or
	[Engine]
	StateColor=1


Development team
----------------

- Daniel Roux
- Denis Dumoulin
- Michael Walz

Beta testeurs
-------------

- Adrien Roux
- Didier Raboud
- Thierry Raboud
- Frédéric Michot
- Nicolas Farnandez


Developer
----------

EPSITEC SA
Mouette 5
CH-1092 Belmont

buzzingcars@epsitec.ch
www.buzzingcars.com
