=========================
GPU PerfStudio 1.2.51
=========================

GPU PerfStudio is AMD's real-time performance analysis tool which has
been designed to help tune the graphics performance of your D3D9, D3D10
and OpenGL application.  GPU PerfStudio displays real-time API, driver 
and hardware data which can be visualized using extremely flexible
plotting and bar chart mechanisms.  The application being profiled may
be executed locally or remotely over the network.  GPU PerfStudio
allows the developer to override key rendering states in real-time for
rapid bottleneck detection. No special drivers or code modifications
are needed to use GPU PerfStudio.


Setup/Installation
-------------------
GPU PerfStudio requirements:

Windows XP SP2 / Vista (32 bit) 
Radeon 9500 or better (for hardware data on server machine) 
  (CrossFire systems not supported)
CATALYST 7.12 or later (for hardware data on server machine) 

NOTE: Catalyst 7.10 or later is not supported for DX9 applications on systems running
      XP with HD 2000 and HD 3000 family graphics cards; instead use Catalyst 7.9:
      http://ati.amd.com/support/drivers/xp/previous/radeon/radeonxip-cat79-xp.html


Before installing GPU PerfStudio, uninstall all previous versions of
GPU PerfStudio. GPU PerfStudio works best when run remotely. You must
run the GPU PerfStudio installer on both machines - the "client"
machine running the GPU PerfStudio application and the server (target)
machine running the application to be profiled. If you select a custom
install, you can install only the server or client on an individual
machine.

When uninstalling you can ignore messages indicating a reboot is 
necessary.

Connection
-----------
If the connection is not successful, you may receive the message 
"GPU PerfServer not running on <machine name>". This may also mean 
that the machine does not exist or is not available.


Known Issues
------------
You cannot use the supplied app launcher with a batch file or a
launcher application that starts another process (the actual 3D 
application).

GPU PerfStudio can affect some power management functions on the GPU.
If you notice reduced battery life, simply shutdown and boot your 
target machine; uninstalling GPU PerfStudio is not necessary. 

GPU PerfStudio cannot launch DX9 target applications running on Vista 
(Target Application in the Connection menu).

You cannot connect in ALL or HW mode on DX9/Vista target machines; 
consequently, hardware and driver data are not available for DX9/Vista 
applications.

Certain target applications may crash when exiting after GPU PerfStudio 
usage.

The Nvidia firewall (process nsvcAppFlt.exe) must be turned off on both 
client and server machines for GPU PerfStudio to operate properly.

The performance of target applications with high frame rates (> 100 fps) 
may be affected when run with GPU PerfStudio resulting in inaccurate 
analysis.

There are some known issues related to updating and data collection on
multi-monitor machines (one graphics card, two monitors) and 
multi-context applications.

Partially obscuring the target application window can cause GPU
PerfStudio to display incorrect counter information.

If you install a new driver on your target machine, you may need to 
uninstall and reinstall GPU PerfStudio on your target machine to fully 
enable hardware data collection.

On rare occasions, GPU PerfStudio will seem to get stuck during
connection or connection initialization. If this happens, kill the GPU
PerfStudio application on the client machine, then on the server
machine, restart the server from the desktop icon or the Start menu
(Start->All Programs->AMD->GPU PerfStudio 1.1->Restart
Performance Server).

On some older graphics cards, if you use the debug D3D runtime and
"Break on D3D error" is checked, an error will occur in
CreateDevice. This error is benign and can be ignored.

DXDiag can report an out of date version of the D3D runtime; it is 
doing this based on the version number of our capture module. 
Underneath this, the correct version of the D3D runtime will be used.

Known OpenGL Issues
-------------------
In OpenGL mode, the "Force Skip Draw Calls" override will not affect
draw calls made with immediate mode or display lists.

In OpenGL mode, state overrides may not work with applications that use
display lists.

In OpenGL mode, windowed applications may have distorted hardware counter
results.  For best accuracy, run your OpenGL application in full-screen mode.

Contact us 
-----------
We would appreciate any feedback; please send your comments,
suggestions and bug reports to: gputools.support@amd.com