字節太長，所以必須分兩段 ....
---------------part 2-----------------------------

PIX for Windows

For issues specific to Direct3D 10 support in PIX, refer to the “Direct3D 10 Tech Preview” section.
Direct3D objects are not viewable from the context menu until they are valid. An object is valid after you have selected an event after the creation event for the object with the render pane visible.


Pre-release XACT

See the XACT documentation for more information. The XACT documentation is available from the Start Menu after installing the DirectX SDK.
There is no 64-bit support in XACT in this release.
Running the XACT Beta (audio console) results in the Windows Firewall dialog being displayed.
Read-only memory mapped file I/O and read-only memory for sound banks fails in the beta when using variations.
The wet/mix parameter on FX adjust the wet/dry mix in the FX buffer. The main sound buffer always plays at 100% regardless of wet/dry mix. This means if the wet dry mix is at 50% you are in effect sending a weaker double of the original signal out. FX presets are defaulting to a wet/dry mix of 50% and need to be adjusted to 100%. The amount of reverb should be adjusted using the send level. Send level is a new RPC parameter. Send level does not show up in the FX's associated RPC, only in user created RPCs. Create a new RPC and attach your sound to it to adjust send levels via variable adjustments.
There is no support for XACT on pre-release versions of Windows Vista for this release.

Visual Studio 2005

After installing the DirectX SDK, only the Managed DirectX documentation is visible in Visual Studio Express 2005 documentation browser. This will be fixed in a future SDK release.
HLSL syntax highlighting works properly in Visual Studio 2005 but the Direct3D 9 Shader Debugger is not currently supported.
The shader debugging functionality of the DirectX Extensions for Visual Studio does not work with Visual Studio 2005. Syntax highlighting continues to work with Visual Studio 2005.

DXUT

The December SDK contains a new pre-release version of DXUT for Direct3D 10 contained in the (SDK ROOT)\Samples\C++\DXUT folder. This new version supports both Direct3D 9 and Direct3D 10.
The Direct3D9-only version of DXUT remains at (SDK ROOT)\Samples\C++\Common. This version will be removed in the Direct3D 10 Final Release.


Managed DirectX

Pre-release Managed DirectX for Whidbey
Included with the DirectX SDK (December 2005) release is support for the 2.0 Common Language Runtime (CLR) in Managed DirectX. It includes new features designed to take full advantage of the features included in the 2.0 CLR such as generics. Besides support for the 2.0 CLR, this updated assembly has a number of new additions, which we would love feedback on, including better performance, 64-bit support, and a cleaner API.
To use the new assembly, load up Visual Studio 2005, and after creating a new project add a reference to "Microsoft.DirectX.dll" You may see multiple versions of this assembly depending on any past DirectX SDK's you've installed, so add the reference to the one with the version 2.0.0.0. The namespaces you'll find in this assembly are named Microsoft.DirectX.*
Beta versions of 2.0 CLR are not supported in Managed DirectX.


Using the DirectX Control Panel on Windows Vista under a Least-privileged User Account (LUA)

Some settings in the DirectX Control Panel are not available when logged in to the system using an account that doesn't have Administrator rights. To switch between Retail and Debug versions of the Managed DirectX assemblies, you will need to login using an account that has Administrative privileges. An alternative is to launch the DirectX Control Panel via an elevated command window i.e.

1) From the start menu type %systemroot%\system32
2) Right click on cmd.exe
3) Select "Run Elevated" and provide any Administrator account credentials
4) In the command window type directx.cpl (on x64 systems directx64.cpl).

To run x86 version of directx.cpl on x64 systems, type %systemroot%\syswow64 in step #1 and directx.cpl in step #4.

Other settings in the Control Panel that are available can be changed using the normal options, as the changes are made in a virtualized copy of the registry that is managed by the operating system.

Installation Notes
(All Platforms)
This SDK is supported for installation on Windows XP, Windows Server 2003, and Windows Vista December 2005 CTP using Visual Studio .Net 2003 or 2005.

We recommend you remove previous versions of the DirectX SDK prior to installing DirectX SDK release and that includes any DirectX SDK installations that may be part of a Microsoft Platform SDK.

Installation of the Microsoft Platform SDK is recommended and is required for some samples.

SDK Installation to a network share is not supported. Specifically some components (ex. documentation will not install, managed samples will not run).

The Direct3D Reference Rasterizer is not installed on any versions of Windows Server 2003 product family.

Several Virus Protection software applications interfere with SDK installation and may require you to temporarily disable the Virus Protection software until SDK installation is completed.

"A cabinet file is necessary for installation and cannot be trusted." ERROR during installation. This problem happens in most cases due to system corruption or users disabling their cryptography services. Please try the following steps to see if it resolves the issue.

o Make sure your cryptography services are enabled. To do this, go to my computer | manage | services and applications | services. Then go to cryptography services properties and make sure the service is started and startup type is set to automatic.

o If you are running Windows on a FAT32 drive, run scandisk.

o Try the resolution steps in http://support.microsoft.com/defaul...kb;en-us;813442.

o Try the resolution steps in http://support.microsoft.com/defaul...kb;EN-US;822798.

o Remove temporary files in %temp% and (if installing end-user runtime)
%windir%\system32\directx\websetup Error

Installation notes for 64-bit Platforms
· When installing on a 64 platform, both the 32 bit and the 64 bit version of debug files will be installed. The 32-bit version of the DirectX control panel which controls debug settings can be opened by choosing "View x86 Control Panel Icons" from the Control Panel and starting the DirectX icon or by running the command %windir%\syswow64\control.exe %windir%\syswow64\directx.cpl. The 64 bit version of the DirectX control panel will show up in the Windows Control Panel after installing the SDK.

· There is no support for installing the DirectX SDK on IA64 bit platforms.