4/10/2019
Posted by 

File Size: 24.55 MB; Date Released: Oct 25, 2001; Works on: Windows 98 / Windows 2000 / Windows XP / Windows Vista / Windows 7; Doesn't Work on: Add.

Hi,

I am running Windows 7 Ultimate on a Toshiba Satellite A210-11A laptop (which originally came with Windows Vista Home Premium x32-bit preinstalled, but later I clean-installed Windows 7 Ultimate x64-bit, instead). I have been getting a Display error (atikmdag) in Event Viewer that Display is not active, ever since. My Display driver in device Manager is:

Driver Version: 8.632.1.2000
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 8/18/2009.

I searched AMD's and got a list of possible causes, one of which suggests trying to update DirectX. My Dxdiag tells that I am running DirectX 11.

I woul greatly appreciate any help.

Thanks in advance.

Imad.

Here is the DxDiag log:

System Information
------------------
Time of this report: 5/11/2012, 10:08:31
Machine name: HEART-MATE
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120330-1504)
Language: English (Regional Setting: English)
System Manufacturer: XXXXXX
System Model: Satellite A210
BIOS: Ver 1.00PARTTBL
Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-58 (2 CPUs), ~1.9GHz
Memory: 4094MB RAM
Available OS Memory: 4094MB RAM
Page File: 2003MB used, 6182MB available
Windows Dir: C:Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: ATI Mobility Radeon HD 2600
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x9581)
DAC type: Internal DAC(400MHz)
Device Key: EnumPCIVEN_1002&DEV_9581&SUBSYS_FF001179&REV_00
Display Memory: 2034 MB
Dedicated Memory: 243 MB
Shared Memory: 1791 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: LPLDD00
Native Mode: 1280 x 800(p) (59.910Hz)
Output Type: Internal
Driver Name: atiumd64.dll,atidxx64.dll,atiumdag,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.14.0010.0678 (English)
Driver Version: 8.632.1.2000
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 8/18/2009 02:15:58, 4059648 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-D6C1-11CF-6F70-0ADFA1C2C535}
Vendor ID: 0x1002
Device ID: 0x9581
SubSys ID: 0xFF001179
Revision ID: 0x0000
Driver Strong Name: oem3.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_M76:8.632.1.2000:pciven_1002&dev_9581
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0268&SUBSYS_1179FF0C&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5904 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 8/3/2009 15:40:16, 1966624 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
Description: Microphone (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5904 (English)
Driver Attributes: Final Retail
Date and Size: 8/3/2009 15:40:16, 1966624 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
Vendor/Product ID: 0x1002, 0x4389
Matching Device ID: usbroot_hub
Service: usbhub
Driver: usbhub.sys, 3/25/2011 06:29:26, 343040 bytes
Driver: usbd.sys, 3/25/2011 06:28:59, 7936 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Standard PS/2 Keyboard
Matching Device ID: *pnp0303
Service: i8042prt
Driver: i8042prt.sys, 7/14/2009 02:19:57, 105472 bytes
Driver: kbdclass.sys, 7/14/2009 04:48:04, 50768 bytes

+ Terminal Server Keyboard Driver
Matching Device ID: rootrdp_kbd
Upper Filters: kbdclass
Service: TermDD
Driver: i8042prt.sys, 7/14/2009 02:19:57, 105472 bytes
Driver: kbdclass.sys, 7/14/2009 04:48:04, 50768 bytes

+ Synaptics PS/2 Port TouchPad
Matching Device ID: *syn0705
Upper Filters: SynTP
Service: i8042prt

+ Microsoft Compact Optical Mouse 500 v2.0 (IntelliPoint)
Vendor/Product ID: 0x045E, 0x0737
Matching Device ID: hidvid_045e&pid_0737
Upper Filters: Point64
Service: mouhid
Driver: point64.sys, 8/1/2011 15:59:06, 45416 bytes
Driver: mouhid.sys, 7/14/2009 03:00:20, 31232 bytes
Driver: mouclass.sys, 7/14/2009 04:48:27, 49216 bytes
Driver: wdfcoinstaller01009.dll, 4/13/2011 15:04:38, 1721576 bytes

+ Terminal Server Mouse Driver
Matching Device ID: rootrdp_mou
Upper Filters: mouclass
Service: TermDD
Driver: termdd.sys, 11/20/2010 16:33:57, 63360 bytes
Driver: sermouse.sys, 7/14/2009 03:00:20, 26624 bytes
Driver: mouclass.sys, 7/14/2009 04:48:27, 49216 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 35.4 GB
Total Space: 76.8 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Drive: D:
Free Space: 39.8 GB
Total Space: 41.0 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Drive: E:
Free Space: 13.1 GB
Total Space: 15.4 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Flexisign crack 10. Drive: F:
Free Space: 14.8 GB
Total Space: 25.6 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Drive: G:
Free Space: 25.3 GB
Total Space: 41.0 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Drive: H:
Free Space: 5.6 GB
Total Space: 20.5 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

Drive: I:
Free Space: 13.1 GB
Total Space: 16.7 GB
File System: NTFS
Model: FUJITSU MHX2250BT ATA Device

--------------
System Devices
--------------
Name: AMD Miscellaneous Configuration
Device ID: PCIVEN_1022&DEV_1103&SUBSYS_00000000&REV_003&2411E6FE&1&C3
Driver: n/a

Name: PCI Express standard Root Port
Device ID: PCIVEN_1002&DEV_7915&SUBSYS_FF001179&REV_003&2411E6FE&1&28
Driver: C:Windowssystem32DRIVERSpci.sys, 6.01.7601.17514 (English), 11/20/2010 16:33:48, 184704 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCIVEN_1002&DEV_4388&SUBSYS_FF001179&REV_003&2411E6FE&1&99
Driver: C:Windowssystem32driversusbohci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 25600 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

Name: AMD DRAM and HyperTransport(tm) Trace Mode Configuration
Device ID: PCIVEN_1022&DEV_1102&SUBSYS_00000000&REV_003&2411E6FE&1&C2
Driver: n/a

Name: PCI Express standard Root Port
Device ID: PCIVEN_1002&DEV_7913&SUBSYS_FF001179&REV_003&2411E6FE&1&10
Driver: C:Windowssystem32DRIVERSpci.sys, 6.01.7601.17514 (English), 11/20/2010 16:33:48, 184704 bytes

Directx windows 8.1 64 bit

Name: Standard OpenHCD USB Host Controller
Device ID: PCIVEN_1002&DEV_4387&SUBSYS_FF001179&REV_003&2411E6FE&1&98
Driver: C:Windowssystem32driversusbohci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 25600 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

Name: Atheros AR5007EG Wireless Network Adapter
Device ID: PCIVEN_168C&DEV_001C&SUBSYS_7128144F&REV_014&27FE42A4&0&0038
Driver: C:Windowssystem32DRIVERSathrx.sys, 9.02.0000.0419 (English), 5/24/2011 00:24:22, 2750464 bytes
Driver: C:Windowssystem32driversvwifibus.sys, 6.01.7600.16385 (English), 7/14/2009 03:07:21, 24576 bytes

Name: AMD Address Map Configuration
Device ID: PCIVEN_1022&DEV_1101&SUBSYS_00000000&REV_003&2411E6FE&1&C1
Driver: n/a

Name: PCI standard host CPU bridge
Device ID: PCIVEN_1002&DEV_7910&SUBSYS_FF001179&REV_003&2411E6FE&1&00
Driver: n/a

Directx 8.1 Windows 7 Ultimate

Name: Standard Enhanced PCI to USB Host Controller
Device ID: PCIVEN_1002&DEV_4386&SUBSYS_FF001179&REV_003&2411E6FE&1&9D
Driver: C:Windowssystem32driversusbehci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 52736 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

Beatmania iidx 16 empress ps2 iso

Name: Realtek PCIe FE Family Controller
Device ID: PCIVEN_10EC&DEV_8136&SUBSYS_FF001179&REV_010200000010EC813600
Driver: C:Windowssystem32DRIVERSRt64win7.sys, 7.03.0522.2009 (English), 5/22/2009 22:52:30, 215040 bytes
Driver: C:Windowssystem32RtNicProp64.dll, 1.02.0000.0003 (English), 3/5/2009 14:54:58, 67584 bytes

Name: AMD HyperTransport(tm) Configuration
Device ID: PCIVEN_1022&DEV_1100&SUBSYS_00000000&REV_003&2411E6FE&1&C0
Driver: n/a

Name: ATI I/O Communications Processor LPC Controller
Device ID: PCIVEN_1002&DEV_438D&SUBSYS_FF001179&REV_003&2411E6FE&1&A3
Driver: C:Windowssystem32DRIVERSmsisadrv.sys, 6.01.7600.16385 (English), 7/14/2009 04:48:27, 15424 bytes

Name: ATI I/O Communications Processor SMBus Controller
Device ID: PCIVEN_1002&DEV_4385&SUBSYS_FF001179&REV_143&2411E6FE&1&A0
Driver: n/a

Name: SDA Standard Compliant SD Host Controller
Device ID: PCIVEN_104C&DEV_803C&SUBSYS_FF001179&REV_004&1A5DE67B&0&23A4
Driver: C:Windowssystem32DRIVERSsdbus.sys, 6.01.7601.17514 (English), 11/20/2010 12:37:42, 109056 bytes

Name: High Definition Audio Controller
Device ID: PCIVEN_1002&DEV_AA08&SUBSYS_AA081002&REV_004&CD27BB3&0&0110
Driver: C:Windowssystem32DRIVERShdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010 13:43:43, 122368 bytes

Name: Standard Dual Channel PCI IDE Controller
Device ID: PCIVEN_1002&DEV_438C&SUBSYS_FF001179&REV_003&2411E6FE&1&A1
Driver: C:Windowssystem32DRIVERSpciide.sys, 6.01.7600.16385 (English), 7/14/2009 04:45:45, 12352 bytes
Driver: C:Windowssystem32DRIVERSpciidex.sys, 6.01.7600.16385 (English), 7/14/2009 04:45:46, 48720 bytes
Driver: C:Windowssystem32DRIVERSatapi.sys, 6.01.7600.16385 (English), 7/14/2009 04:52:21, 24128 bytes
Driver: C:Windowssystem32DRIVERSataport.sys, 6.01.7601.17514 (English), 11/20/2010 16:32:46, 155520 bytes

Name: ATI I/O Communications Processor PCI Bus Controller
Device ID: PCIVEN_1002&DEV_4384&SUBSYS_00000000&REV_003&2411E6FE&1&A4
Driver: C:Windowssystem32DRIVERSpci.sys, 6.01.7601.17514 (English), 11/20/2010 16:33:48, 184704 bytes

Name: Texas Instruments PCIxx12 Integrated FlashMedia Controller
Device ID: PCIVEN_104C&DEV_803B&SUBSYS_FF001179&REV_004&1A5DE67B&0&22A4
Driver: n/a

Name: ATI Mobility Radeon HD 2600
Device ID: PCIVEN_1002&DEV_9581&SUBSYS_FF001179&REV_004&CD27BB3&0&0010
Driver: C:Windowssystem32DRIVERSatikmdag.sys, 8.01.0001.0921 (English), 8/18/2009 03:48:48, 6037504 bytes
Driver: C:Windowssystem32DRIVERSati2erec.dll, 1.00.0000.0019 (English), 8/18/2009 01:37:56, 53248 bytes
Driver: C:Windowssystem32atiumd64.dll, 8.14.0010.0678 (English), 8/18/2009 02:15:58, 4059648 bytes
Driver: C:Windowssystem32atiumd6a.dll, 8.14.0010.0228 (English), 8/18/2009 02:10:52, 2622976 bytes
Driver: C:Windowssystem32atitmm64.dll, 6.14.0011.0022 (English), 8/18/2009 02:35:12, 120320 bytes
Driver: C:Windowssystem32atiicdxx.dat, 6/18/2009 19:29:04, 197654 bytes
Driver: C:Windowssystem32amdpcom64.dll, 8.14.0010.0023 (English), 8/18/2009 01:52:50, 52224 bytes
Driver: C:Windowssystem32atimpc64.dll, 8.14.0010.0023 (English), 8/18/2009 01:52:50, 52224 bytes
Driver: C:Windowssystem32atiadlxx.dll, 6.14.0010.1050 (English), 8/18/2009 01:52:18, 251904 bytes
Driver: C:Windowssystem32atiumd6a.cap, 8/18/2009 02:08:34, 219120 bytes
Driver: C:Windowssystem32atimuixx.dll, 6.14.0010.1001 (English), 8/18/2009 02:34:24, 12288 bytes
Driver: C:Windowssystem32atiesrxx.exe, 6.14.0011.1033 (English), 8/18/2009 02:36:20, 203264 bytes
Driver: C:Windowssystem32atieclxx.exe, 6.14.0011.1033 (English), 8/18/2009 02:36:54, 420352 bytes
Driver: C:Windowssystem32atipdl64.dll, 6.14.0010.2556 (English), 8/18/2009 02:34:52, 421376 bytes
Driver: C:Windowssystem32atiedu64.dll, 6.14.0010.2514 (English), 8/18/2009 02:34:20, 59392 bytes
Driver: C:Windowssystem32ATIDEMGX.dll, 2.00.3516.38910 (English), 8/18/2009 02:37:02, 442368 bytes
Driver: C:Windowssystem32atio6axx.dll, 6.14.0010.8787 (English), 8/18/2009 02:33:44, 15062016 bytes
Driver: C:Windowssystem32aticaldd64.dll, 6.14.0010.0344 (English), 8/18/2009 01:49:22, 4289536 bytes
Driver: C:Windowssystem32aticalrt64.dll, 6.14.0010.0344 (English), 8/18/2009 01:49:46, 48640 bytes
Driver: C:Windowssystem32aticalcl64.dll, 6.14.0010.0344 (English), 8/18/2009 01:49:34, 41984 bytes
Driver: C:Windowssystem32atibtmon.exe, 2.00.0000.0000 (English), 5/11/2009 21:35:30, 118784 bytes
Driver: C:Windowssystem32atidxx64.dll, 8.15.0010.0212 (English), 8/18/2009 02:26:18, 2921984 bytes
Driver: C:WindowsSysWOW64atiumdag.dll, 8.14.0010.0678 (English), 8/18/2009 02:20:38, 3105280 bytes
Driver: C:WindowsSysWOW64atiumdva.dll, 8.14.0010.0228 (English), 8/18/2009 02:05:32, 2868736 bytes
Driver: C:WindowsSysWOW64amdpcom32.dll, 8.14.0010.0023 (English), 8/18/2009 01:52:44, 51712 bytes
Driver: C:WindowsSysWOW64atimpc32.dll, 8.14.0010.0023 (English), 8/18/2009 01:52:44, 51712 bytes
Driver: C:WindowsSysWOW64atiadlxy.dll, 6.14.0010.1050 (English), 8/18/2009 01:52:10, 184320 bytes
Driver: C:WindowsSysWOW64atiumdva.cap, 8/18/2009 02:05:02, 219120 bytes
Driver: C:WindowsSysWOW64atipdlxx.dll, 6.14.0010.2556 (English), 8/18/2009 02:34:46, 356352 bytes
Driver: C:WindowsSysWOW64Oemdspif.dll, 6.15.0006.0005 (English), 8/18/2009 02:34:32, 274432 bytes
Driver: C:WindowsSysWOW64ati2edxx.dll, 6.14.0010.2514 (English), 8/18/2009 02:34:16, 43520 bytes
Driver: C:WindowsSysWOW64atioglxx.dll, 6.14.0010.8787 (English), 8/18/2009 02:11:52, 11650560 bytes
Driver: C:WindowsSysWOW64atidxx32.dll, 8.15.0010.0212 (English), 8/18/2009 02:31:32, 2469888 bytes
Driver: C:WindowsSysWOW64aticaldd.dll, 6.14.0010.0344 (English), 8/18/2009 01:48:28, 3264512 bytes
Driver: C:WindowsSysWOW64aticalrt.dll, 6.14.0010.0344 (English), 8/18/2009 01:49:44, 53248 bytes
Driver: C:WindowsSysWOW64aticalcl.dll, 6.14.0010.0344 (English), 8/18/2009 01:49:32, 53248 bytes
Driver: C:Windowsatiogl.xml, 6/17/2009 07:53:12, 18333 bytes
Driver: C:Windowssystem32ATIODCLI.exe, 1.00.0000.0001 (English), 2/3/2009 20:52:08, 51200 bytes
Driver: C:Windowssystem32ATIODE.exe, 1.00.0000.0001 (English), 2/18/2009 17:55:24, 332288 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCIVEN_1002&DEV_438B&SUBSYS_FF001179&REV_003&2411E6FE&1&9C
Driver: C:Windowssystem32driversusbohci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 25600 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

Name: High Definition Audio Controller
Device ID: PCIVEN_1002&DEV_4383&SUBSYS_FF081179&REV_003&2411E6FE&1&A2
Driver: C:Windowssystem32DRIVERShdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010 13:43:43, 122368 bytes

Name: Texas Instruments 1394 OHCI Compliant Host Controller
Device ID: PCIVEN_104C&DEV_803A&SUBSYS_FF001179&REV_004&1A5DE67B&0&21A4
Driver: C:Windowssystem32DRIVERS1394ohci.sys, 6.01.7601.17514 (English), 11/20/2010 13:44:56, 229888 bytes

Name: PCI Express standard Root Port
Device ID: PCIVEN_1002&DEV_7917&SUBSYS_FF001179&REV_003&2411E6FE&1&38
Driver: C:Windowssystem32DRIVERSpci.sys, 6.01.7601.17514 (English), 11/20/2010 16:33:48, 184704 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCIVEN_1002&DEV_438A&SUBSYS_FF001179&REV_003&2411E6FE&1&9B
Driver: C:Windowssystem32driversusbohci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 25600 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

Name: Standard Dual Channel PCI IDE Controller
Device ID: PCIVEN_1002&DEV_4380&SUBSYS_FF001179&REV_003&2411E6FE&1&90
Driver: C:Windowssystem32DRIVERSpciide.sys, 6.01.7600.16385 (English), 7/14/2009 04:45:45, 12352 bytes
Driver: C:Windowssystem32DRIVERSpciidex.sys, 6.01.7600.16385 (English), 7/14/2009 04:45:46, 48720 bytes
Driver: C:Windowssystem32DRIVERSatapi.sys, 6.01.7600.16385 (English), 7/14/2009 04:52:21, 24128 bytes
Driver: C:Windowssystem32DRIVERSataport.sys, 6.01.7601.17514 (English), 11/20/2010 16:32:46, 155520 bytes

Name: Texas Instruments PCI-8x12/7x12/6x12 CardBus Controller
Device ID: PCIVEN_104C&DEV_8039&SUBSYS_FF001179&REV_004&1A5DE67B&0&20A4
Driver: C:Windowssystem32DRIVERSpcmcia.sys, 6.01.7600.16385 (English), 7/14/2009 04:45:45, 220752 bytes

Name: PCI Express standard Root Port
Device ID: PCIVEN_1002&DEV_7916&SUBSYS_FF001179&REV_003&2411E6FE&1&30
Driver: C:Windowssystem32DRIVERSpci.sys, 6.01.7601.17514 (English), 11/20/2010 16:33:48, 184704 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCIVEN_1002&DEV_4389&SUBSYS_FF001179&REV_003&2411E6FE&1&9A
Driver: C:Windowssystem32driversusbohci.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:04, 25600 bytes
Driver: C:Windowssystem32driversusbport.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:14, 325120 bytes
Driver: C:Windowssystem32driversusbhub.sys, 6.01.7601.17586 (English), 3/25/2011 06:29:26, 343040 bytes

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,6.01.7601.17514
WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,6.01.7601.17514
WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,6.01.7601.17514
MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,6.01.7600.16385
Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,6.01.7600.16385
WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,6.01.7601.17514
WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,6.01.7601.17514
Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,6.01.7600.16385
Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,6.01.7600.16385
DV Muxer,0x00400000,0,0,qdv.dll,6.06.7601.17514
Color Space Converter,0x00400001,1,1,quartz.dll,6.06.7601.17713
WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.7601.17514
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,12.00.7601.17514
AVI Splitter,0x00600000,1,1,quartz.dll,6.06.7601.17713
VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,6.06.7601.17713
SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,6.01.7140.0000
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.7601.17528
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft TV Captions Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7601.17715
MJPEG Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.17713
CBVA DMO wrapper filter,0x00200000,1,1,cbva.dll,6.01.7601.17514
MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,6.06.7601.17713
SAMI (CC) Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.7601.17528
Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,6.06.7601.17514
SBE2FileScan,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17514
Internal Script Command Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG Audio Decoder,0x03680001,1,1,quartz.dll,6.06.7601.17713
DV Splitter,0x00600000,1,2,qdv.dll,6.06.7601.17514
Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,6.06.7601.17713
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,6.01.7601.17514
ACM Wrapper,0x00600000,1,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.7601.17528
Line 21 Decoder,0x00600000,1,1,,
Video Port Manager,0x00600000,2,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00400000,1,0,quartz.dll,6.06.7601.17713
VPS Decoder,0x00200000,0,0,WSTPager.ax,6.06.7601.17514
WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.7601.17514
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.01.7601.17514
File writer,0x00200000,1,0,qcap.dll,6.06.7601.17514
iTV Data Sink,0x00600000,1,0,itvdata.dll,6.06.7601.17514
iTV Data Capture filter,0x00600000,1,1,itvdata.dll,6.06.7601.17514
DVD Navigator,0x00200000,0,3,qdvd.dll,6.06.7601.17713
Microsoft TV Subtitles Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7601.17715
Overlay Mixer2,0x00200000,1,1,,
RDP DShow Redirection Filter,0xffffffff,1,0,DShowRdpFilter.dll,
Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17514
WST Pager,0x00200000,1,1,WSTPager.ax,6.06.7601.17514
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.7601.17528
DV Video Decoder,0x00800000,1,1,qdv.dll,6.06.7601.17514
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.7601.17514
Null Renderer,0x00200000,1,0,qedit.dll,6.06.7601.17514
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.7601.17514
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,6.01.7601.17514
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.7601.17528
Smart Tee,0x00200000,1,2,qcap.dll,6.06.7601.17514
Overlay Mixer,0x00200000,0,0,,
AVI Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.17713
NetBridge,0x00200000,2,0,netbridge.dll,6.01.7601.17514
AVI/WAV File Source,0x00400000,0,2,quartz.dll,6.06.7601.17713
Wave Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
MIDI Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
Multi-file Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
File stream renderer,0x00400000,1,1,quartz.dll,6.06.7601.17713
Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,6.01.7140.0000
StreamBufferSink2,0x00200000,0,0,sbe.dll,6.06.7601.17528
AVI Mux,0x00200000,1,0,qcap.dll,6.06.7601.17514
Line 21 Decoder 2,0x00600002,1,1,quartz.dll,6.06.7601.17713
File Source (Async.),0x00400000,0,1,quartz.dll,6.06.7601.17713
File Source (URL),0x00400000,0,1,quartz.dll,6.06.7601.17713
Media Center Extender Encryption Filter,0x00200000,2,2,Mcx2Filter.dll,6.01.7601.17514
AudioRecorder WAV Dest,0x00200000,0,0,WavDest.dll,
AudioRecorder Wave Form,0x00200000,0,0,WavDest.dll,
SoundRecorder Null Renderer,0x00200000,0,0,WavDest.dll,
Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,6.06.7601.17514
Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.01.7601.17514
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.7601.17669
MPEG Video Decoder,0x40000001,1,1,quartz.dll,6.06.7601.17713

WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,6.01.7600.16385
WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,6.01.7600.16385
MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,6.01.7600.16385
DV Video Encoder,0x00200000,0,0,qdv.dll,6.06.7601.17514
MJPEG Compressor,0x00200000,0,0,quartz.dll,6.06.7601.17713

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,6.01.7600.16385
WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,6.01.7600.16385
IMA ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
PCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
Microsoft ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
GSM 6.10,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT A-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT u-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
MPEG Layer-3,0x00200000,1,1,quartz.dll,6.06.7601.17713

Audio Capture Sources:
Microphone (Realtek High Defini,0x00200000,0,0,qcap.dll,6.06.7601.17514

PBDA CP Filters:
PBDA DTFilter,0x00600000,1,1,CPFilters.dll,6.06.7601.17528
PBDA ETFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17528
PBDA PTFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17528

Midi Renderers:
Default MidiOut Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,6.06.7601.17713

WDM Streaming Capture Devices:
,0x00000000,0,0,,
,0x00000000,0,0,,
Chicony USB 2.0 Camera,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Directx 8.1 Windows 7 Ultimate

WDM Streaming Rendering Devices:
Realtek HDA HDMI Out,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.7601.17514

Video Capture Sources:
Chicony USB 2.0 Camera,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.7601.17669
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.7601.17514

BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,1,EncDec.dll,6.06.7601.17708
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.7601.17708
PTFilter,0x00200000,0,0,EncDec.dll,6.06.7601.17708
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.7601.17708

WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Audio Renderers:
Speakers (Realtek High Definiti,0x00200000,1,0,quartz.dll,6.06.7601.17713
Default DirectSound Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Default WaveOut Device,0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: Speakers (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,6.06.7601.17713

---------------
EVR Power Information
---------------
Current Setting: {651288E5-A7ED-4076-A96B-6CC62D848FE1} (Balanced)
Quality Flags: 2576
Enabled:
Force throttling
Allow half deinterlace
Allow scaling
Decode Power Usage: 100
Balanced Flags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 50
PowerFlags: 1424
Enabled:
Force throttling
Allow batching
Force half deinterlace
Force scaling
Decode Power Usage: 0

Jump to navigationJump to search
DirectX
Operating systemMicrosoft Windows
TypeAPI
Websitewww.microsoft.com/en-us/download/details.aspx?id=35%2C+https%3A%2F%2Fwww.microsoft.com%2Fja-jp%2Fdirectx%2F

Microsoft DirectX is a collection of application programming interfaces (APIs) for handling tasks related to multimedia, especially game programming and video, on Microsoft platforms. Originally, the names of these APIs all began with Direct, such as Direct3D, DirectDraw, DirectMusic, DirectPlay, DirectSound, and so forth. The name DirectX was coined as a shorthand term for all of these APIs (the X standing in for the particular API names) and soon became the name of the collection. When Microsoft later set out to develop a gaming console, the X was used as the basis of the name Xbox to indicate that the console was based on DirectX technology.[1] The X initial has been carried forward in the naming of APIs designed for the Xbox such as XInput and the Cross-platform Audio Creation Tool (XACT), while the DirectX pattern has been continued for Windows APIs such as Direct2D and DirectWrite. Cara upgrade tanaka t22 hd jurassic 2017.

Direct3D (the 3D graphics API within DirectX) is widely used in the development of video games for Microsoft Windows and the Xbox line of consoles. Direct3D is also used by other software applications for visualization and graphics tasks such as CAD/CAM engineering. As Direct3D is the most widely publicized component of DirectX, it is common to see the names 'DirectX' and 'Direct3D' used interchangeably.

The DirectX software development kit (SDK) consists of runtime libraries in redistributable binary form, along with accompanying documentation and headers for use in coding. Originally, the runtimes were only installed by games or explicitly by the user. Windows 95 did not launch with DirectX, but DirectX was included with Windows 95 OEM Service Release 2.[2]Windows 98 and Windows NT 4.0 both shipped with DirectX, as has every version of Windows released since. The SDK is available as a free download. While the runtimes are proprietary, closed-source software, source code is provided for most of the SDK samples. Starting with the release of Windows 8 Developer Preview, DirectX SDK has been integrated into Windows SDK.[3]

  • 1Development history
  • 3Versions
  • 4Compatibility

Development history[edit]

In late 1994, Microsoft was ready to release Windows 95, its next operating system. An important factor in the value consumers would place on it was the programs that would be able to run on it. Three Microsoft employees—Craig Eisler, Alex St. John, and Eric Engstrom—were concerned because programmers tended to see Microsoft's previous operating system, MS-DOS, as a better platform for game programming, meaning few games would be developed for Windows 95 and the operating system would not be as much of a success. This was compounded by negative reception surrounding the Windows port of the video game The Lion King. The game used WinG, which crashed on Compaq Presarios that came shipped with it following a partnership between Compaq and Disney, as the Cirrus Logic display drivers used by the Presarios were not thoroughly tested with the API.[4]

DOS allowed direct access to video cards, keyboards, mice, sound devices, and all other parts of the system, while Windows 95—with its protected memory model—restricted access to all of these, working on a much more standardized model. Microsoft needed a quick solution for programmers; the operating system was only months away from being released. Eisler (development lead), St. John, and Engstrom (program manager) worked together to fix this problem, with a solution that they eventually named DirectX.

Descargar Directx 8.1 Para Windows 7 Ultimate

Ultimate

The first version of DirectX was released in September 1995 as the Windows Games SDK. It was the Win32 replacement for the DCI[5] and WinG APIs for Windows 3.1. DirectX allowed all versions of Microsoft Windows, starting with Windows 95, to incorporate high-performance multimedia. Eisler wrote about the frenzy to build DirectX 1 through 5 in his blog.[6]

DirectX 2.0 became a component of Windows itself with the releases of Windows 95 OSR2 and Windows NT 4.0 in mid-1996. Since Windows 95 was itself still new and few games had been released for it, Microsoft engaged in heavy promotion of DirectX to developers who were generally distrustful of Microsoft's ability to build a gaming platform in Windows. Alex St. John, the evangelist for DirectX, staged an elaborate event at the 1996 Computer Game Developers Conference which game developer Jay Barnson described as a Roman theme, including real lions, togas, and something resembling an indoor carnival.[7] It was at this event that Microsoft first introduced Direct3D and DirectPlay, and demonstrated multiplayer MechWarrior 2 being played over the Internet.

The DirectX team faced the challenging task of testing each DirectX release against an array of computer hardware and software. A variety of different graphics cards, audio cards, motherboards, CPUs, input devices, games, and other multimedia applications were tested with each beta and final release. The DirectX team also built and distributed tests that allowed the hardware industry to confirm that new hardware designs and driver releases would be compatible with DirectX.

Prior to DirectX, Microsoft had included OpenGL on their Windows NT platform.[8] At the time, OpenGL required 'high-end' hardware and was focused on engineering and CAD uses.[citation needed] Direct3D was intended to be a Microsoft controlled alternative to OpenGL, focused initially on game use. As 3D gaming grew, OpenGL developed to include better support for programming techniques for interactive multimedia applications like games, giving developers choice between using OpenGL or Direct3D as the 3D graphics API for their applications. At that point a 'battle' began between supporters of the cross-platform OpenGL and the Windows-only Direct3D. Incidentally, OpenGL was supported at Microsoft by the DirectX team. If a developer chose to use OpenGL 3D graphics API, the other APIs of DirectX are often combined with OpenGL in computer games because OpenGL does not include all of DirectX's functionality (such as sound or joystick support).

In a console-specific version, DirectX was used as a basis for Microsoft's Xbox, Xbox 360 and Xbox Oneconsole API. The API was developed jointly between Microsoft and Nvidia, which developed the custom graphics hardware used by the original Xbox. The Xbox API was similar to DirectX version 8.1, but is non-updateable like other console technologies. The Xbox was code named DirectXbox, but this was shortened to Xbox for its commercial name.[9]

In 2002, Microsoft released DirectX 9 with support for the use of much longer shader programs than before with pixel and vertex shader version 2.0. Microsoft has continued to update the DirectX suite since then, introducing Shader Model 3.0 in DirectX 9.0c, released in August 2004.

As of April 2005, DirectShow was removed from DirectX and moved to the Microsoft Platform SDK instead.

DirectX has been confirmed to be present in Microsoft's Windows Phone 8.[10]

Real-time raytracing was announced as DXR in 2018.

Logos[edit]

The original logo resembled a deformed radiation warning symbol. Controversially, the original name for the DirectX project was the 'Manhattan Project', a reference to the US nuclear weapons initiative. Alex St. John, head of Microsoft DirectX evangelism at the time, claims[11] that the connotation of the ultimate outcome of the Manhattan Project (the nuclear bombing of Japan) is intentional, and that DirectX and its sister project, the Xbox (which shares a similar logo), were meant to displace Japanese videogame-makers from their dominance of the video-game industry.[12] However, Microsoft publicly denies this account, instead claiming that the logo is merely an artistic design.[12]

  • DirectX 1.0–8.2

  • DirectX 9.0–12

Components[edit]

DirectX is composed of multiple APIs:

  • Direct3D (D3D): for drawing 3D graphics.
  • DXGI: for enumerating adapters and monitors and managing swap chains for Direct3D 10 and up.
  • Direct2D: for 2D graphics.
  • DirectWrite: for fonts.
  • DirectCompute: for GPU Computing.
  • DirectX Diagnostics (DxDiag): a tool for diagnosing and generating reports on components related to DirectX, such as audio, video, and input drivers.
  • DirectX Media Objects: support for streaming objects such as encoders, decoders, and effects.
  • DirectSetup: for the installation of DirectX components, and the detection of the current DirectX version.
  • XACT3 higher-level audio API.
  • XAudio2: low-level API for audio.
  • DirectX Raytracing (DXR): real-time raytracing for DirectX 12.

Microsoft has deprecated, but still supports, these DirectX components:

  • DirectX Media: comprising DirectAnimation for 2D/3D[13] web animation, DirectShow for multimedia playback and streaming media, DirectX Transform for web interactivity, and Direct3D Retained Mode for higher level 3D graphics. It also contained DirectX plugins for audio signal processing and DirectX Video Acceleration for accelerated video playback. Deprecated in favor of Media Foundation.
  • DirectDraw: for drawing 2D Graphics (raster graphics). Deprecated in favor of Direct2D, though still in use by a number of games and as a video renderer in media applications.
  • DirectInput: for interfacing with input devices including keyboards, mice, joysticks, or other game controllers. Deprecated after version 8 in favor of XInput for Xbox 360 controllers or standard WM_INPUT window message processing for keyboard and mouse input.
  • DirectPlay: for communication over a local-area or wide-area network. Deprecated after version 8 in favor of Games for Windows Live and Xbox Live.
  • DirectSound: for the playback and recording of waveform sounds. Deprecated since DirectX 8 in favor of XAudio2 and XACT3.
  • DirectSound3D (DS3D): for the playback of 3D sounds. Deprecated since DirectX 8 in favor of XAudio2 and XACT3.
  • DirectMusic: for playback of soundtracks authored in DirectMusic Producer. Deprecated since DirectX 8 in favor of XAudio2 and XACT3.

DirectX functionality is provided in the form of COM-style objects and interfaces. Additionally, while not DirectX components themselves, managed objects have been built on top of some parts of DirectX, such as Managed Direct3D[14] and the XNA graphics library[15] on top of Direct3D 9.

Versions[edit]

DirectX 9[edit]

DirectX 9 was released in 2002 for Windows 98 through XP, and currently on or supported by all subsequent versions. Microsoft continues to make changes in DirectX 9c, causing support to be dropped for some of the aforementioned operating systems. As of January 2007, Windows 2000 or XP is required. This also introduced Pixel Shader 2.0.

DirectX 10[edit]

See also: Direct3D 10
Microsoft DirectX 10 logo wordmark

A major update to DirectX API, DirectX 10 ships with and is only available with Windows Vista and later; previous versions of Windows such as Windows XP are not able to run DirectX 10-exclusive applications. Rather, programs that are run on a Windows XP system with DirectX 10 hardware simply resort to the DirectX 9.0c code path, the latest available for Windows XP computers.[16]

Changes for DirectX 10 were extensive. Many former parts of DirectX API were deprecated in the latest DirectX SDK and are preserved for compatibility only: DirectInput was deprecated in favor of XInput, DirectSound was deprecated in favor of the Cross-platform Audio Creation Tool system (XACT) and additionally lost support for hardware accelerated audio, since the Vista audio stack renders sound in software on the CPU. The DirectPlay DPLAY.DLL was also removed and was replaced with dplayx.dll; games that rely on this DLL must duplicate it and rename it to dplay.dll.

In order to achieve backwards compatibility, DirectX in Windows Vista contains several versions of Direct3D:[17]

  • Direct3D 9: emulates Direct3D 9 behavior as it was on Windows XP. Details and advantages of Vista's Windows Display Driver Model are hidden from the application if WDDM drivers are installed. This is the only API available if there are only XP graphic drivers (XDDM) installed, after an upgrade to Vista for example.
  • Direct3D 9Ex (known internally during Windows Vista development as 9.0L or 9.L): allows full access to the new capabilities of WDDM (if WDDM drivers are installed) while maintaining compatibility for existing Direct3D applications. The Windows Aero user interface relies on D3D 9Ex.
  • Direct3D 10: Designed around the new driver model in Windows Vista and featuring a number of improvements to rendering capabilities and flexibility, including Shader Model 4.

Reinstall Directx Windows 8.1

Direct3D 10.1 is an incremental update of Direct3D 10.0 which shipped with, and required, Windows Vista Service Pack 1.[18] This release mainly sets a few more image quality standards for graphics vendors, while giving developers more control over image quality.[19] It also adds support for cube map arrays, separate blend modes per-MRT, coverage mask export from a pixel shader, ability to run pixel shader per sample, access to multi-sampled depth buffers[20] and requires that the video card supports Shader Model 4.1 or higher and 32-bit floating-point operations. Direct3D 10.1 still fully supports Direct3D 10 hardware, but in order to utilize all of the new features, updated hardware is required.[21]

DirectX 11[edit]

See also: Direct3D 11
Microsoft DirectX 11 logo wordmark

Microsoft unveiled DirectX 11 at the Gamefest 08 event in Seattle, with the major scheduled features including GPGPU support (DirectCompute), and Direct3D 11 with tessellation support[22][23] and improved multi-threading support to assist video game developers in developing games that better utilize multi-core processors.[24] Direct3D 11 runs on Windows Vista, Windows 7, Windows 8 and Windows 10. Parts of the new API such as multi-threaded resource handling can be supported on Direct3D 9/10/10.1-class hardware. Hardware tessellation and Shader Model 5.0 require Direct3D 11 supporting hardware.[25] Microsoft has since released the Direct3D 11 Technical Preview.[26] Direct3D 11 is a strict superset of Direct3D 10.1 — all hardware and API features of version 10.1 are retained, and new features are added only when necessary for exposing new functionality. This helps to keep backwards compatibility with previous versions of DirectX.

Microsoft released the Final Platform Update for Windows Vista on October 27, 2009, which was 5 days after the initial release of Windows 7 (launched with Direct3D 11 as a base standard).

Since then, four updates for DirectX 11 were released:

  • DirectX 11.1 is included in Windows 8. It supports WDDM 1.2 for increased performance, features improved integration of Direct2D (now at version 1.1), Direct3D, and DirectCompute, and includes DirectXMath, XAudio2, and XInput libraries from the XNA framework. It also features stereoscopic 3D support for gaming and video.[27] DirectX 11.1 was also partially backported to Windows 7, via the Windows 7 platform update.[28][29]
  • DirectX 11.2 is included in Windows 8.1 (including the RT version) and Windows Server 2012 R2.[30] It added some new features to Direct2D like geometry realizations.[31] It also added swap chain composition, which allows some elements of the scene to be rendered at lower resolutions and then composited via hardware overlay with other parts rendered at higher resolution.[32]
  • DirectX 11.X is a superset of DirectX 11.2 running on the Xbox One.[33] It actually includes some features, such as draw bundles, that were later announced as part of DirectX 12.[34]
  • DirectX 11.3 was announced along with DirectX 12 at GDC and released in 2015. It is meant to complement DirectX 12 as a higher-level alternative.[35] It is included with Windows 10.[30]

DirectX 12[edit]

See also: Direct3D 12

DirectX 12 was announced by Microsoft at GDC on March 20, 2014, and was officially launched alongside Windows 10 on July 29, 2015.

The primary feature highlight for the new release of DirectX was the introduction of advanced low-level programming APIs for Direct3D 12 which can reduce driver overhead. Developers are now able to implement their own command lists and buffers to the GPU, allowing for more efficient resource utilization through parallel computation. Lead developer Max McMullen stated that the main goal of Direct3D 12 is to achieve 'console-level efficiency on phone, tablet and PC'.[36] The release of Direct3D 12 comes alongside other initiatives for low-overhead graphics APIs including AMD's Mantle for AMD graphics cards, Apple's Metal for iOS and macOS and Khronos Group's cross-platform Vulkan.

Multiadapter support will feature in DirectX 12 allowing developers to utilize multiple GPUs on a system simultaneously; multi-GPU support was previously dependent on vendor implementations such as AMD CrossFireX or NVIDIA SLI.[37][38][39][40]

Implicit Multiadapter support will work in a similar manner to previous versions of DirectX where frames are rendered alternately across linked GPUs of similar compute-power.
Explicit Multiadapter will provide two distinct API patterns to developers. Linked GPUs will allow DirectX to view graphics cards in SLI or CrossFireX as a single GPU and use the combined resources. Whereas Unlinked GPUs will allow GPUs from different vendors to be utilized by DirectX, such as supplementing the dedicated GPU with the integrated GPU on the CPU, or combining AMD and NVIDIA cards. However, elaborate mixed multi-GPU setups requires significantly more attentive developer support.

DirectX 12 is supported on all Fermi and later Nvidia GPUs, on AMD's GCN-based chips and on Intel's Haswell and later processors' graphics units.[41]

At SIGGRAPH 2014, Intel released a demo showing a computer generated asteroid field, in which DirectX 12 was claimed to be 50–70% more efficient than DirectX 11 in rendering speed and CPU power consumption.[42][43]

Ashes of the Singularity was the first publicly available game to utilize DirectX 12. Testing by Ars Technica in August 2015 revealed slight performance regressions in DirectX 12 over DirectX 11 mode for the Nvidia GeForce 980 Ti, whereas the AMD Radeon R9 290x achieved consistent performance improvements of up to 70% under DirectX 12, and in some scenarios the AMD outperformed the more powerful Nvidia under DirectX 12. The performance discrepancies may be due to poor Nvidia driver optimizations for DirectX 12, or even hardware limitations of the card which was optimized for DirectX 11 serial execution, however the exact cause remains unclear.[44]

DirectX 12 APIs are also featured on the Xbox, however the DirectX 12 code is not directly portable between PC and Xbox One due to inherent differences between the two platforms.[45][46] The performance improvements of DirectX 12 on the Xbox are not as substantial as on the PC.[47]

In March 2018, DirectX Raytracing (DXR) was announced, capable of real-time ray-tracing on supported hardware,[48] and the DXR API was added in the Windows 10 October 2018 update.

In 2019 Microsoft announced the arrival of DirectX 12 to Windows 7[49]


Release history[edit]

Table of DirectX versions
DirectX versionVersion numberRelease dateNotes
1.04.02.0095September 30, 1995
2.01996Was shipped only with a few 3rd party applications
2.0a4.03.00.1096June 5, 1996Windows 95 OSR2 and Windows NT 4.0
3.04.04.00.0068September 15, 1996
4.04.00.00691996Later package of DirectX 3.0 included Direct3D 4.04.00.0069
3.0a4.04.00.0070December 1996Windows NT 4.0 SP3 (and above)
Last supported version of DirectX for Windows NT 4.0
3.0b4.04.00.0070December 1996This was a very minor update to 3.0a that fixed a cosmetic problem with the Japanese version of Windows 95
4.0Never launchedDirectX 4 was never released. Raymond Chen of Microsoft explained in his book, The Old New Thing, that after DirectX 3 was released, Microsoft began developing versions 4 and 5 at the same time. Version 4 was to be a shorter-term release with small features, whereas version 5 would be a more substantial release. The lack of interest from game developers in the features stated for DirectX 4 resulted in it being shelved, and the corpus of documents that already distinguished the two new versions resulted in Microsoft choosing to not re-use version 4 to describe features intended for version 5.[50][51]
5.04.05.00.0155 (RC55)August 4, 1997Available as a beta for Windows 2000 that would install on Windows NT 4.0
5.24.05.01.1600 (RC00)May 5, 1998DirectX 5.2 release for Windows 95
4.05.01.1998 (RC0)June 25, 1998Windows 98 exclusive
6.04.06.00.0318 (RC3)August 7, 1998Windows CE as implemented on Dreamcast
6.14.06.02.0436 (RC0)February 3, 1999
6.1a4.06.03.0518 (RC0)May 5, 1999Windows 98 Second Edition exclusive
7.04.07.00.0700 (RC1)September 22, 1999
4.07.00.0700February 17, 2000Windows 2000
7.0a4.07.00.0716 (RC0)March 8, 2000
4.07.00.0716 (RC1)2000
7.14.07.01.3000 (RC1)September 14, 2000Windows ME exclusive. Last version to have built-in RGB software rendering support
8.04.08.00.0400 (RC10)November 12, 2000
8.0a4.08.00.0400 (RC14)February 5, 2001Last supported version for Windows 95 and last version to have software rendering support in dxdiag.exe
8.14.08.01.0810October 25, 2001Windows XP, Windows XP SP1, Windows Server 2003 and Xbox exclusive
4.08.01.0881 (RC7)November 8, 2001This version is for the down level operating systems (Windows 98, Windows ME and Windows 2000)
8.1a4.08.01.0901 (RC?)2002This release includes an update to Direct3D (D3d8.dll)
8.1b4.08.01.0901 (RC7)June 25, 2002This update includes a fix to DirectShow on Windows 2000 (Quartz.dll)
8.24.08.02.0134 (RC0)2002Same as the DirectX 8.1b but includes DirectPlay 8.2
9.04.09.00.0900 (RC4)December 19, 2002Periodic updates were released for DirectX 9, starting from 4.09.00.0904 (RC0 for DX 9.0c) in October 2004, released bimonthly until August 2007, and quarterly thereafter. The last periodic update was released in June 2010[52]

The February 9, 2005 release is the first 64-bit capable build.[53] The last build for Windows 98SE/Me is the redistributable from December 13, 2006.[54][55] The last build for Windows 2000 is the redistributable from February 5, 2010.[56] April 2006 is the first official support to Windows Vista[57] and August 2009 is the first official support to Windows 7 and DX11 update[58]

9.0a4.09.00.0901 (RC6)March 26, 2003
9.0b4.09.00.0902 (RC2)August 13, 2003
9.0c[59]July 22, 2004First 9.0c version and last supported version for Windows 98[60]
4.09.00.0903Windows XP SP2 exclusive
4.09.00.0904 (RC0)August 4, 2004
December 8, 2006Last supported version for Windows 98 Second Edition[60]
4.09.00.0904August 6, 2004 / April 21, 2008*Xbox 360, Windows XP SP2, SP3*, Windows Server 2003 SP1 and Windows Server 2003 R2
October 27, 2008Last supported version for Windows ME
106.00.6000.16386November 30, 2006Windows Vista exclusive
10.16.00.6001.18000February 4, 2008Windows Vista SP1, Windows Server 2008
Includes Direct3D 10.1
6.00.6002.18005April 28, 2009Windows Vista SP2, Windows Server 2008 SP2
Includes Direct3D 10.1
116.01.7600.16385October 22, 2009Windows 7, Windows Server 2008 R2
6.00.6002.18107October 27, 2009Windows Vista SP2 and Windows Server 2008 SP2, through the Platform Update for Windows Vista and Windows Server 2008[61]
6.01.7601.17514February 16, 2011Windows 7 SP1, Windows Server 2008 R2 SP1
11.16.02.9200.16384August 1, 2012Windows 7 SP1, Windows 8, Windows RT, Windows Server 2012
11.26.03.9600.16384October 18, 2013Windows 8.1, Windows RT, Windows Server 2012 R2, Xbox One
12.010.00.10240.16384July 29, 2015Windows 10, Xbox One
10.00.15063.0000March 20, 2017Windows 10, Depth Bounds Testing and Programmable MSAA added[62][63]
10.00.17763.0001October 2, 2018Windows 10, DirectX Raytracing support added[64]

The version number as reported by Microsoft's DxDiag tool (version 4.09.0000.0900 and higher) use the x.xx.xxxx.xxxx format for version numbers. However, the DirectX and Windows XP MSDN page claims that the registry always has been in the x.xx.xx.xxxx format. Put another way, when the above table lists a version as '4.09.00.0904' Microsoft's DxDiag tool may have it as '4.09.0000.0904'.[65]

Compatibility[edit]

Various releases of Windows have included and supported various versions of DirectX, allowing newer versions of the operating system to continue running applications designed for earlier versions of DirectX until those versions can be gradually phased out in favor of newer APIs, drivers, and hardware.

APIs such as Direct3D and DirectSound need to interact with hardware, and they do this through a device driver. Hardware manufacturers have to write these drivers for a particular DirectX version's device driver interface (or DDI), and test each individual piece of hardware to make them DirectX compatible. Some hardware devices have only DirectX compatible drivers (in other words, one must install DirectX in order to use that hardware). Early versions of DirectX included an up-to-date library of all of the DirectX compatible drivers currently available. This practice was stopped however, in favor of the web-based Windows Update driver-update system, which allowed users to download only the drivers relevant to their hardware, rather than the entire library.

Prior to DirectX 10, DirectX runtime was designed to be backward compatible with older drivers, meaning that newer versions of the APIs were designed to interoperate with older drivers written against a previous version's DDI. The application programmer had to query the available hardware capabilities using a complex system of 'cap bits' each tied to a particular hardware feature. Direct3D 7 and earlier would work on any version of the DDI, Direct3D 8 requires a minimum DDI level of 6 and Direct3D 9 requires a minimum DDI level of 7.[66]However, the Direct3D 10 runtime in Windows Vista cannot run on older hardware drivers due to the significantly updated DDI, which requires a unified feature set and abandons the use of 'cap bits'.

Direct3D 10.1 introduces 'feature levels' 10_0 and 10_1, which allow use of only the hardware features defined in the specified version of Direct3D API. Direct3D 11 adds level 11_0 and '10 Level 9' - a subset of the Direct3D 10 API designed to run on Direct3D 9 hardware, which has three feature levels (9_1, 9_2 and 9_3) grouped by common capabilities of 'low', 'med' and 'high-end' video cards; the runtime directly uses Direct3D 9 DDI provided in all WDDM drivers. Feature level 11_1 has been introduced with Direct3D 11.1.

.NET Framework[edit]

In 2002, Microsoft released a version of DirectX compatible with the Microsoft .NET Framework, thus allowing programmers to take advantage of DirectX functionality from within .NET applications using compatible languages such as managed C++ or the use of the C# programming language. This API was known as 'Managed DirectX' (or MDX for short), and claimed to operate at 98% of performance of the underlying native DirectX APIs. In December 2005, February 2006, April 2006, and August 2006, Microsoft released successive updates to this library, culminating in a beta version called Managed DirectX 2.0. While Managed DirectX 2.0 consolidated functionality that had previously been scattered over multiple assemblies into a single assembly, thus simplifying dependencies on it for software developers, development on this version has subsequently been discontinued, and it is no longer supported. The Managed DirectX 2.0 library expired on October 5, 2006.

During the GDC 2006, Microsoft presented the XNA Framework, a new managed version of DirectX (similar but not identical to Managed DirectX) that is intended to assist development of games by making it easier to integrate DirectX, High-Level Shader Language (HLSL) and other tools in one package. It also supports the execution of managed code on the Xbox 360. The XNA Game Studio Express RTM was made available on December 11, 2006, as a free download for Windows XP. Unlike the DirectX runtime, Managed DirectX, XNA Framework or the Xbox 360 APIs (XInput, XACT etc.) have not shipped as part of Windows. Developers are expected to redistribute the runtime components along with their games or applications.

No Microsoft product including the latest XNA releases provides DirectX 10 support for the .NET Framework.

The other approach for DirectX in managed languages is to use third-party libraries like:

  • SlimDX, an open source library for DirectX programming on the .NET Framework
  • SharpDX,[67][68] which is an open source project delivering the full DirectX API for .NET on all Windows platforms, allowing the development of high performance game, 2D and 3D graphics rendering as well as real-time sound applications
  • DirectShow.NET for the DirectShow subset
  • Windows API CodePack for .NET Framework, which is an open source library from Microsoft.

Alternatives[edit]

There are alternatives to the DirectX family of APIs, with OpenGL, its successor Vulkan, Metal and Mantle having the most features comparable to Direct3D. Examples of other APIs include Glide, SDL, Allegro, OpenMAX, OpenML, OpenAL, OpenCL, FMOD, SFML etc. Many of these libraries are cross-platform or have open codebases. There are also alternative implementations that aim to provide the same API, such as the one in Wine. Furthermore, the developers of ReactOS are trying to reimplement DirectX under the name 'ReactX'.

See also[edit]

  • Graphics Device Interface (GDI)

References[edit]

  1. ^'Microsoft: The meaning of Xbox - The Economist'. The Economist.
  2. ^'DirectX Help'. computerhope.com.
  3. ^'Where is the DirectX SDK?'. microsoft.com. Microsoft.
  4. ^Tynan, Dan (26 May 2006). 'The 25 Worst Tech Products of All Time'. PC World. Retrieved 20 September 2015.
  5. ^'54 What is DCI?'. stason.org.
  6. ^Craig Eisler's blog post about the frenzy to build DirectX 1 through 5 on craig.theeislers.com
  7. ^Jay Barnson (July 13, 2006). 'Tales of the Rampant Coyote'. Archived from the original on July 17, 2006.
  8. ^'Windows NT 3.51 Product Overview'. Microsoft. 31 October 2006. Archived from the original on 29 November 2012. Retrieved 16 September 2010.
  9. ^J. Allard, PC Pro InterviewArchived 2007-10-11 at the Wayback Machine, April 2004
  10. ^'Windows Phone 8 adds DirectX, native development, easier app porting'. June 20, 2012. Retrieved June 23, 2012.
  11. ^'Alex St John Interview'. March 28, 2007. Retrieved 31 August 2011.
  12. ^ abDavid Craddock (March 2007). 'Alex St John Interview, page 2'. Shack News. Archived from the original on 2008-06-01.
  13. ^3D Animation of SPACE FIGHTER by DIRECT ANIMATION[permanent dead link]
  14. ^'DirectX 9: Using the Managed Direct3D Graphics API in .NET'. microsoft.com. Microsoft.
  15. ^'Microsoft.Xna.Framework.Graphics Namespace'. microsoft.com. Microsoft.
  16. ^'DirectX Frequently Asked Questions'. microsoft.com. Microsoft.
  17. ^Chuck Walbourn (August 2009). 'Graphics APIs in Windows'. MSDN. Retrieved 2009-10-03.
  18. ^Albanesius, Chloe (2007-08-29). 'Microsoft Unleashes First Service Pack for Vista'. PC Magazine. Retrieved 2007-08-29.
  19. ^'Microsoft Presents DirectX 10.1 Details at SIGGRAPH'. 2007-08-07. Retrieved 2007-08-27.
  20. ^'Learn Network Inspire'(PDF). AMD. Archived from the original(PDF) on 2012-04-10. Retrieved 2012-12-30.
  21. ^'DirectX 10.1 Requires No New GPU'. Windows Vista: The Complete Guide. 2008-03-05. Archived from the original on 2007-10-29. Retrieved 2008-03-05.
  22. ^'What's next for DirectX? A DirectX 11 overview — A DirectX 11 overview'. Elite Bastards. September 1, 2008. Retrieved 2008-09-04.
  23. ^'DirectX 11: A look at what's coming'. bit-tech.net. September 17, 2008.
  24. ^Windows 7 and D3D 11 release dateArchived 2011-10-09 at the Wayback Machine
  25. ^'MSDN Blogs'. msdn.com. Microsoft.
  26. ^'Download DirectX Software Development Kit from Official Microsoft Download Center'. microsoft.com. Microsoft.
  27. ^Windows 8 Developer Preview GuideArchived 2011-10-07 at the Wayback Machine
  28. ^'Platform Update for Windows 7 (Windows)'. Msdn.microsoft.com. Retrieved 2014-08-09.
  29. ^Pooya Eimandar (2013). DirectX 11.1 Game Programming. Packt Publishing Ltd. p. 45. ISBN978-1-84969-481-0.
  30. ^ ab'How to install the latest version of DirectX'. Microsoft Support. Microsoft. Retrieved 27 October 2017.
  31. ^'Geometry Realizations Overview'. microsoft.com. Microsoft.
  32. ^Bennett Sorbo (June 26, 2013). 'What's New in Direct3D 11.2'. Channel9 - BUILD 2013. around 20:00.
  33. ^'Microsoft officially turns down Mantle'. semiaccurate.com.
  34. ^Chris Tector's segment of http://channel9.msdn.com/Blogs/DirectX-Developer-Blog/DirectX-Evolving-Microsoft-s-Graphics-Platform (starting approx. 18 minute in.)
  35. ^Smith, Ryan (September 18, 2014). 'Microsoft Details Direct3D 11.3 & 12 New Rendering Features'. AnandTech. Retrieved November 6, 2014.
  36. ^McMullen, Max (2 April 2014). 'Direct3D 12 API Preview'. Channel 9. Microsoft.
  37. ^Moore, Bo (May 5, 2015). 'DirectX 12 will be able to use your integrated GPU to improve performance'. PC Gamer. Future US. Retrieved August 22, 2015.
  38. ^Michaud, Scott (May 4, 2015). 'BUILD 2015: The Final DirectX 12 Reveal'. PC Perspective. PC Perspective. Retrieved August 22, 2015.
  39. ^Langley, Bryan (July 29, 2015). 'Windows 10 and DirectX 12 released!'. MSDN DirectX Developer Blog. Microsoft. Retrieved August 22, 2015.
  40. ^Yeung, Andrew (April 30, 2015). 'DirectX 12 Multiadapter: Lighting up dormant silicon and making it work for you'. MSDN DirectX Developer Blog. Microsoft. Retrieved August 22, 2015.
  41. ^Ryan Smith. 'AnandTech - Microsoft Announces DirectX 12: Low Level Graphics Programming Comes To DirectX'. anandtech.com.
  42. ^Yeung, Andrew (13 August 2014). 'DirectX 12 – High Performance and High Power Savings'. DirectX Developer Blog. Microsoft.
  43. ^Lauritzen, Andrew (11 August 2014). 'SIGGRAPH 2014: DirectX 12 on Intel'. Developer Zone. Intel.
  44. ^Walton, Mark (August 19, 2015). 'DirectX 12 tested: An early win for AMD, and disappointment for Nvidia'. Ars Technica UK. Retrieved August 19, 2015.
  45. ^'GoW4 Dev on DX12 Performance Boosts, Xbox One S, ESRAM & Ultimate Edition PC Issues'. Retrieved July 15, 2018.
  46. ^'id Software Dev Puzzled By Devs Choosing DX12 Over Vulkan, Claims Xbox One DX12 Is Different Than PC « GamingBolt.com: Video Game News, Reviews, Previews and Blog'. gamingbolt.com. Retrieved 2017-03-01.
  47. ^'Xbox One chief warns gamers not to expect dramatic improvements from DirectX 12 - ExtremeTech'. ExtremeTech. Retrieved 30 September 2014.
  48. ^'Announcing Microsoft DirectX Raytracing!'. Microsoft.
  49. ^'Microsoft ports DirectX 12 to Windows 7, giving some older PC games a performance boost'. PCWorld. 2019-03-13. Retrieved 2019-04-17.
  50. ^Chen, Raymond (2006). 'Etymology and History'. The Old New Thing (1st ed.). Pearson Education. p. 330. ISBN0-321-44030-7.
  51. ^'What happened to DirectX 4? - The Old New Thing - Site Home - MSDN Blogs'. Blogs.msdn.com. 2004-01-22. Retrieved 2012-12-30.
  52. ^'Download DirectX End-User Runtimes (June 2010) from Official Microsoft Download Center'. microsoft.com. Microsoft.
  53. ^Direct link toArchived 2006-05-09 at the Wayback Machinelast pure 32-bit DirectX 9.0c from December 13, 2004Archived 2006-05-08 at the Wayback Machine & Direct link toArchived 2011-06-04 at the Wayback Machinefirst 64-bit capable DirectX 9.0c from February 9, 2005Archived 2009-10-16 at the Wayback Machine
  54. ^'DirectX End-User Runtimes – December 2006'. Download Center. Microsoft. 13 December 2006. Retrieved 7 February 2015.
  55. ^'DirectX End-User Runtimes – February 2007'. Download Center. Microsoft. 13 February 2007. Retrieved 7 February 2015.
  56. ^'Download DirectX End-User Runtimes (February 2010) from Official Microsoft Download Center'. microsoft.com. Microsoft.
  57. ^'DirectX End-User Runtimes (April 2006) Full Download'. Download Center. Microsoft. 6 April 2006. Retrieved 7 February 2015.
  58. ^'Download DirectX End-User Runtimes (March 2009) from Official Microsoft Download Center'. microsoft.com. Microsoft.
  59. ^'Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center'. microsoft.com. Microsoft.
  60. ^ ab'MicroSoft DirectX Downloads for Windows (Win95, Win98, Win98SE, WinME, Win2000, WinXP) - complete release history including DirectX1, DirectX2, DirectX3, DirectX5, DirecX6, DirecX7, DirecX8, DirecX9'. falconfly.3dfx.pl. Retrieved 2018-08-05.
  61. ^'Microsoft upgrades Windows Vista with DirectX 11'. pcgameshardware.com.
  62. ^https://docs.microsoft.com/en-us/windows/uwp/whats-new/windows-10-build-15063
  63. ^https://blogs.msdn.microsoft.com/directx/2017/11/07/announcing-new-directx-12-features/
  64. ^https://blogs.msdn.microsoft.com/directx/2018/10/02/directx-raytracing-and-the-windows-10-october-2018-update/
  65. ^DirectX and Windows XP[permanent dead link]
  66. ^MSN. 'Minimum DDI requirements'. Microsoft. Retrieved 2 August 2012.
  67. ^'SharpDX - Managed DirectX'. Retrieved 30 September 2014.
  68. ^'sharpdx/SharpDX'. GitHub. Retrieved 30 September 2014.

External links[edit]

  • DirectX at Curlie
Retrieved from 'https://en.wikipedia.org/w/index.php?title=DirectX&oldid=897840597'
Categories:
Hidden categories:
Socorro Diez Elsa Bornemann Pdf