Debugging the precompute

The more complex stages of the precompute generate debugging information that can be useful in visualising the process and understanding the behaviour of the systems. Much of this information is incorporated into the GeoRadiosity visualisation services, which you can use with your own scenes. As your integration progresses, you will probably want to use this debugging information to implement visualisations within your own game engine or editor.

Data generation

The High Level Build System automatically creates these debugging data objects in the radiosity folder of the scene output.

If you are using the Low Level Precompute API, you must call additional functions during the precompute to generate the data. For example:

virtual Geo::s32 CompileLightTransportOutput(
		const IPrecompSystemLightTransport* pLightTransport,
		Geo::IGeoProgressProxy* logger,
		ILightTransportOutput*& oLightTransportOutput) = 0;

For details of the Compile...Output functions, refer to the IPrecompute class; there is one function for each object that has debugging information available.

Debugging objects

The three main debugging objects are as follows:

For more information, see the low level precompute API and Debugging Utilities module in the API reference documentation.