Operating Systems:

Windows 2000
Windows XP

Detailed Description
Issues Addressed in This Release
Fixed minor memory leak in imhidusb.sys kernel-mode component
(TT1274).

Known Issues For This Release

Vibration-only devices cannot produce the full spectrum of existing
force feedback effects. Some games make extensive use of spring and
damper effects, and these effects cannot be reproduced on
vibration-only devices. Therefore, when a vibration-only device is
used with these games, fewer sensations will be felt than would be
available with a full-featured force feedback device.

Vibration-only devices do not fully support triggered effects (TT1327)
- This is a known issue that is currently being investigated.
Triggered effects are used sparingly (if at all) in most PC games, so
the user will not notice this in most gameplay situations.

Wheel forces feel different in Need For Speed - Porsche Unleashed when
using DirectX7, DirectX8 (TT1121) - When DX7 is installed on a user's
system, when playing Need For Speed - Porsche Unleashed, some force
effects are not mapped from the Y axis to the X (or wheel) axis. When
using DX8, all force effects are mapped to the X axis. This is a game
programming issue that Immersion has no control over, therefore
Immersion knows of no workaround for this issue.

Immersion Reference Control Panel - Combined/separate pedals, input
display shows crosshair stuck at bottom when DirectX8.1 installed
(TT1161) - In Windows XP, and in Windows 2000 with DirectX8.1
installed, the control panel Input Test page may show no Y-axis
(combined brake/accelerator) movement when the driver is first
installed. This is a DirectX8.1 issue that Microsoft may be planning
to fix in their DirectX9 release. The workaround - reboot the system.
After a reboot, the input display should show full movement in all
axes.

Windows XP - In Gaming Options, Immersion Reference Control Panel
fails to launch if Properties button clicked right after device
appears in listbox (TT1162) - This only happens if a user tries to
view a game controller's properties within the first few seconds after
having plugged in the USB game controller. It seems that the Gaming
Options panel presents the newly-found device in the listbox well
before the driver has finished installing and loading. Workaround -
wait a few seconds after device plugin before attempting to click the
Properties button for that device.

Geoff Crammond's Grand Prix 4 has a problem where if you mis-configure
a joystick or switch joysticks after configuration, the game may lock
up when you try to run it (TT1798) -. If you experience such a problem
you should go to the game's folder and delete the file "F1GSTATE.SAV".
This wipes out the configuration settings and allows you to run the
game.

Supported Devices
Cyborg 3D Force Stick
Cyborg 3D Force Stick (USB)
Cyborg Gold Joystick
P750 Gamepad
pp7 - dont try programming it
R440 Force Wheel
R440 Force Wheel (USB)
Saitek Action Pad USB
Saitek Cyborg 3D Digital Stick II
Saitek Cyborg 3D Rumble Force Joystick
Saitek Cyborg Digital II Stick USB
Saitek Cyborg Evo
Saitek Cyborg Evo Force Joystick
Saitek Cyborg Evo Force Joystick (USB)
Saitek Cyborg Evo Wireless
Saitek Cyborg Force Rumble Pad
Saitek Cyborg Graphite Stick USB
Saitek Gamers' Keyboard
Saitek GM2 Action Pad USB
Saitek GM2 Mouse USB
Saitek Lan Party
Saitek Magic Joystick
Saitek P2000 Tilt Pad
Saitek P2000 Tilt Pad USB
Saitek P3000 Wireless Pad
Saitek P3000 Wireless Pad USB
Saitek P750 Pad USB
Saitek P880 Pad USB
Saitek PC Dash 2 USB
Saitek R100 Sports Wheel USB
Saitek R440 Force Wheel
Saitek ST290
Saitek X36 Flight Controller
Saitek X45 Flight Controller
Saitek X45 Flight Controller USB
ST 330 Rumble Force Stick (USB)
X36F Flightstick