source: GTP/trunk/App/Demos/Illum/PathMap/ReadMe.txt @ 1480

GameTools standalone tool:

Real-time global illumination
#############################


Provided effect:
#################

Indirect illumination with Precomputed Radiance Maps (PRM)

Standalone final rendering (real time GI) application without or with [if
GENERATE_PATH_MAPS is defined in PathMapEffect.cpp] PRM precomputing


Algorithm benefits:
###################
Provides real-time indirect illumination. As opposed to static light maps,
actual lighting conditions influence indirect illumination. The effect is
achieved by combining multiple 'PRM panes' (partial "light maps") according to
current illumination of 'entry point clusters'.

As opposed to PRT (precomputed radiance transfer), no tessellation (finite
elements) is needed, and near light sources are handled. (We do not assume
infinitely distant
environment lighting.)

Accuracy of PRMs depends on the number of entry points used, influencing
preocessing time only.

Final rendering requires a compositing of PRMs, where performance depends on the
number of 'entry point clusters' considered for an object. As many texture
fetches as clusters are needed. A lower number of clusters will result in
indirect illumination which is less responsive to actual lighting, but still
plausible. (A single cluster would reproduce a static light map which is scaled
according to the total direct illumination.)


Build:
######
This is a standalone DirectX 9.0 application, compiles under Visual C++ 2003
with DirectX SDK April 2006 (identical to June 2006).

Parameters (PRM resolution, shadow map resolution, #entry points, #clusters,
etc.) are hardcoded as #define directives in PathMapEffect.h.

GENERATE_PATH_MAPS in PathMapEffect.cpp must be defined to perform precomputing,
outputting textures to the PRM subfolder. Otherwise, PRM textures are loaded
from the PRM subfolder.


Usage notes:
############
- as precomputing is used, this tool should be used for static level geometry
- multiple static objects are supported and encouraged: every object will use a
set of most important PRM panes
- models must have unique texture mapping (just like light maps)

- there is no support for any particular 'level geometry' discription format.
DirectX .x files and referenced textures are loaded from code.
- To include the method in a particular engine, the level geometry should be
used to compose the scene which is used to generate the PRM textures. Final
compositing must be implemented in the shader system of the game engine,
assigning the computed PRMs to the respective objects as textures.