Return true and the display mode added the array

virtual bool ValidateDisplayMode(const D3DDISPLAYMODE& Mode ) { return true; }

virtual bool ValidateDevice(const D3DDEVTYPE& Type, const D3DCAPS9& Caps ) { return true; }

virtual bool ValidateDepthStencilFormat(const D3DFORMAT& DepthStencilFormat)

{return true;}

In CGameApp.h we derive a class from the CD3DInitialization class:

class CMyD3DInit : public CD3DInitialize { private: virtual bool ValidateDisplayMode ( const D3DDISPLAYMODE& Mode ); virtual bool ValidateDevice ( const D3DDEVTYPE& Type, const D3DCAPS9& Caps ); virtual bool ValidateVertexProcessingType ( const VERTEXPROCESSING_TYPE& Type ); };

TeamLRN

above example, a 320x200 video mode would be rejected and thus not be added to the CD3DInitialize database.

The last function we override in our demo is the ValidateVertexProcessingType. It allows us to reject any devices that do not support the required vertex processing support (eg. hardware transformation and lighting). It can also be used to remove unnecessary processing types. For example, our application does not need a device that supports mixed vertex processing.

Over 10 Million Study Resources Now at Your Fingertips