D3DX Updates

* UVAtlas API - These new API's automatically generate a unique UV texture mapping for an arbitrary mesh, maximizing texture space usage and minimizing texture undersampling (stretch).

* Reduced effects memory footprint - A new flag (D3DXFX_NOT_CLONEABLE) has been added to allow users to specify that an effect will never need to be cloned by the effect system. Using this flag can notably reduce the memory footprint for an effect.

* The precomputed radiance transfer (PRT) system has been enhanced with fast raytracing methods have been added for direct computation of ray/mesh intersections against a simulation scene.

Documentation Updates

* Setup documentation - The DXSetup documentation has been updated to explain the redist naming scheme and how you can customize the redist to reduce your installation size.

DXUT Updates

* Callback functions now pass a void* pUserContext that allows the callback functions to receive context from the application.

* The framework's GUI is now separate and optional from the core framework.

* The framework now allows applications to reject device changes via LPDXUTCALLBACKMODIFYDEVICESETTINGS which returns a bool.

* Passing 0 as the width and height to DXUTCreateDevice now creates a backbuffer of the same size as the client window.

* DXUTGetExitCode now returns 11 if the last device was a D3DDEVTYPE_REF device type.

Technical Article Updates

* The DirectX developer Frequenty Asked Questions (FAQs) page has been added to the documentation.

* A new technical article about the Windows XP Media Center Edition 2005 has been added.

PIX Tool Updates

* You can now open full-stream capture PIXRun files, and render frames from them within PIX, the same way you can with single-frame capture PIXRun files.

* You can save rendered frames to an image file from within PIX.

* You can adjust the scaling of the Y-axis of the event timeline to see data graphed more clearly.

DirectX Component Status

* Microsoft DirectPlay is deprecated, and Microsoft strongly recommends against using it to develop new applications. Game developers should instead use enhanced core Microsoft Windows networking technologies.

* Microsoft DirectInput, Microsoft DirectMusic, Microsoft DirectShow, and Microsoft DirectSound will maintain their current status until new technology in these areas is made available.

* Use of Microsoft DirectDraw is no longer recommended. With the release of DirectX 9.0, all two-dimensional (2-D) functionality is contained within Microsoft Direct3D and its associated helper functions in D3DX. However, the DirectDraw documentation is still available and can be viewed at the MSDN Library Archive at DirectDraw.